TYPO3 Core

mmh, sorry, wrong category... this bug should be "core" ...
found no way to change this like in bugzilla...

Reiner

Whoo, this bug is quite old, but nevertheless, I am interested in the topic.
I can't understand the question 100%, what exactly is the difference between HTTP_HOST and SERVER_NAME?
How are they build in Apache / PHP?
Some docs (Redhat for example) say, both are the same, some say, they are not.

I am a bit confused.

Hello,

first, since 2 weeks we have now consolidated our 2 servers, because our still non typo3 members need more hard disk space and the old one is over 5 years old (ah, and my written "greatest" was with the meaning "biggest" ;-)... )

And second, I hope this ist a clearer explanation...

client -> apache1 -> apache2

client:
Webbrowser who request for instance http://www.dlrg.de/Ueber_uns/

apache1
Frontend webserver who get the request (with HTTP_HOST=www.dlrg.de
and SERVER_NAME=www.dlrg.de) and therefore look after
+ <document root>/Ueber_uns/
but couldn't find the directory of this request...

Normally the apache should rewrite it to the local typo3 instance...
  For bigger sites it could be interesting, to serve the request to a 
  second server (even for load balancing)

So apache1 send a request with a redirect/proxy rule to apache2.

apache2 (who is bound on the second server with IP 10.0.0.4)
Get the request for http://www.dlrg.de/Ueber_uns/ (with
HTTP_HOST=10.0.0.4 and SERVER_NAME=www.dlrg.de)
and therefore look after
+ <document root>/Ueber_uns/
but couldn't find the directory of this request...
This apache2 rewrite it to the local typo3 instance...

If apache2 need only one domain to feed, this could be ignored, but it
there were several domains to handle (set domain records in typo3)
it could'nt detect the original requested domain, because
TYPO3_HOST_ONLY was set to HTTP_HOST instead of
SERVER_NAME. So typo3 delivers the first root typo3 page...

We had the luck that only one domain had to be rewritten the explained
way and that it was the first typo3 page. Our other domains were bound
to another IP, which was handled directly by the apache2 server...

Reiner

IMHO it is possible to rewrite the HTTP_HOST variable:
Read the mod_rewrite docs,
http://httpd.apache.org/docs/1.3/mod/mod_rewrite.html#RewriteRule
Search for the substitution flag [env|E]

I don't know why TYPO3 uses HTTP_HOST instead of SERVER_NAME, but believe there's a reason for it. If the env-rewrite works for you, I will close the bug and mark it as no_change_required.

Still I am interested in how on what basis both ENV get build by PHP...

Using proxies seems to be installation dependent. I just stumbled across a setup with Squid where SERVER_NAME was the same as HOST_NAME, but HTTP_X_FORWARDED_HOST yielded the "correct" name. Incidentally was set HTTP_X_FORWARDED_SERVER too.

So perhaps changing t3lib_div::getIndpEnv() like this is a general solution:

case 'HTTP_HOST':
if ($TYPO3_VAR['SYS']['hostNameVar'] &&
($_SERVER[$TYPO3_VAR['SYS']['hostNameVar']]) {
return $_SERVER[$TYPO3_VAR['SYS']['hostNameVar']]
} else {
return $_SERVER[$getEnvName];
}

As admin you can set now the correct way for your setup (webserver/proxy) to determine the host name.

Equal, if SERVER_NAME or HTTP_HOST is used: It won't work with alle reverse proxy setups.

For use with reverse proxies, there should be an option to configure a hardcoded value for use in TYPO3_HOST_ONLY, TYPO3_PORT and TYPO3_REQUEST_HOST instead of generating one based on HTTP_HOST. These three all take their values from $_SERVER[HTTP_HOST], while all other hostname containing values returned getIndpEnv results use one of these three values.

Our local problem with this issue, is that we always have a "frontend" Apache which serves static content or relays requests to dynamic content to the appropriate PHP or mod_perl "backend" Apache, which usually runs on a higher port. This port then leaks into the front end edit mode via TYPO3_STIE_URL, which is used in full URLs inclusive hostname and port number in JavaScript links.

This seems similar to Bug Id #15135: http://bugs.typo3.org/view.php?id=1699

Hi,

I would like to help on solving the related bugs 169, 1699 and 202. Regarding the reverse proxy capabilities (including SSL) I have started to write a tutorial. The work on this tutorial is necessary for me to understand the problem in depth.

I hope it is also helpful for solving this issue and finding a solution that can be part of the core.

http://www.henningpingel.de/TYPO3-Backend-Via-SSL-Proxy.124.0.html

Best regards,
Henning

duplicate according to Christian Kuhn