[Tickets #1339] HTTP_HOST

[bugs at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/?id=1339
-----------------------------------------------------------------------
 Ticket     | 1339
 Updated By | john at oztralis.com.au
 Summary    | HTTP_HOST
 Queue      | Horde Base
 Version    | 3.0.2
 State      | Feedback
 Priority   | 2. Medium
 Type       | Bug
 Owners     | 
-----------------------------------------------------------------------


john at oztralis.com.au (2005-02-09 13:42) wrote:

in config/hooks.php is an example on how to configure Horde/IMP for virtual
hosts.
it does $vdomain = getenv('HTTP_HOST'); which means the username used to
authenticate agains imap becomes 'user at domain:80' if the host header
includes the port number, EVEN if the port number is 80.

Likewise, in imp/lib/IMP.php in function isPreferredServer() the HTTP_HOST
header is used to determine the mailserver to use, and in
lib/Horde/Auth/radius.php in function _setParams() it is used to set the NAS
identifier.

Under normal circumstances I wouldn't think this would present a problem
since the host header normally doesn't contain a :port number when running
on port 80, but reverse proxies such as Pound (http://apsis.ch/pound) adds
the port number explicitly.

You can test this behaviour by adding :80 to the url in your browser.

I have also noticed another problem, which I believe to be related to
Horde/IMP. since I run other php based solutions on the same backend servers
and have only ever seen this happen with Horde/IMP...:

On occasion, a http request will fail, and either the navigation frame, or
the main frame will fail to load.

using lwp-request to investigate the problem, I get this: 
500 EOF when chunk header expected.


Kind Regards,

John Hansen