Issue Bug Closed

#80148SetEnv HTTPS on breaks host header

Jonny Schulz 03/06/17, 11:34 updated 07/13/17, 11:17

Description

Hi together,

how can it be that SetEnv HTTPS on in apache breaks the host header in Typo3?

Example configuration:

Nginx:
listen 443 ssl;
proxy_set_header Host www.example.net;
proxy_pass http://$backend:8080;

Now if I configure Apache without SetEnv HTTPS on, then I’m able to browse to https://www.example.net/typo3, I’m able to login and if I replace http with https – typo3 redirects to http – all works fine. The next step is to configure SetEnv HTTPS on in Apache, but Typo3 says after that: “The current host header value does not match the configured trusted hosts pattern!”. If I de-configure SetEnv HTTPS on all works fine again with the exception that http is used.

How can it be that the variable HTTPS on breaks the host header?

Regards
Jonny

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.