[TYPO3-core] trustedHostsPattern

[Helmut Hummel]

Hi Joey,

thanks for the inout so far. I still try to understand your setup in 
order to get an idea how we can improve in this area.

On 23.05.14 15:20, JoH asenau wrote:

> The redirect is done on the actual server side.
> Nginx has a rewrite rule checking for missing trailing slashes and
> redirecting them.
> Since there is already a known port in that case, it redirects to
> domain.com:12345/typo3/

can you the essntial parts of the setup?

>> print_r(array_intersect_key($_SERVER,
>> array('HTTP_HOST'=>'','SERVER_NAME'=>'','SERVER_PORT'=>'','REQUEST_URI'=>'','HTTPS'=>'','REMOTE_ADDR'=>'')));
>
> HTTP_HOST
> redaktion.domain.tld
> SERVER_NAME
> redaktion.domain.tld
> SERVER_PORT
> 17101
> REQUEST_URI
> /typo3/install/index.php?TYPO3_INSTALL[type]=phpinfo
> REMOTE_ADDR
> 10.91.65.199

I'm still wondering what setup create such result. You are requesting on 
port 80 but SERVER_PORT is set to 17101 ...

Here my assumptions:

You have a server block configured listening on port 80:

server {
   listen 80;
   root /var/www/redaktion.domain.tld/htdocs;
}

And a server block configured listening on port 17101

server {
   listen 17101;
   root /var/www/redaktion.domain.tld/htdocs;
}

Both apperently hit the TYPO3 installation (if true, why?). How is the 
redirect configured in the server block which listens on port 80?

Are you using the "redirect" directive? How is it set up?

Thanks.

Kind regards,
Helmut

-- 
Helmut Hummel
Release Manager TYPO3 6.0
TYPO3 Core Developer, TYPO3 Security Team Member

TYPO3 .... inspiring people to share!
Get involved: typo3.org