#29693Respect HTTP_X_FORWARDED_PROTO in SSL check
Description
If the webserver runs behind a proxy server which takes care of the SSL encryption, it may forward the HTTP_X_FORWARDED_PROTO header.
However, TYPO3 ignores the header when checking for SSL using t3lib_div::getIndpEnv(‘TYPO3_SSL’).
The header value seems to be a de-facto-standard according to Wikipedia (similar to HTTP_X_FORWARDED_FOR):
http://en.wikipedia.org/wiki/List_of_HTTP_header_fields
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
Related issues 9
- Bug #16395There is a error in detecting the ssl page
- Bug #32341$_SERVER['HTTPS'] vs. $_SERVER['HTTP_HTTPS'] nginx
- Bug #32999Cannot properly handle reverse-proxy as SSL end-point
- Bug #37467Change in class.t3lib_div.php may break things for HTTPS via reverse proxy
- Feature #39016Hook to modify t3lib_div::getIndpEnv return value
- Bug #65334SSL detection: better support for reverse proxies
- Bug #81837SSL mixed content issues in backend when HTTPS server var is not set
- Bug #86264Trusted hosts pattern mismatch with Nginx and HTTP_X_FORWARDED_PORT 443
- Bug #92187HTTP/HTTPS not correctly determined behind reverseProxy