On Thu, 11 Apr 2002, Bill Barker wrote: > We do use the port number from the header, if the port is present. The > current code handles HTTP/1.0 clients much the same way as Http10Interceptor > does. Since the main HTTP/1.0 client that uses Tomcat is Watchdog, I don't > really like enforcing the HTTP/1.1 behavior on HTTP/1.0 clients.
IE/Netscape/Mozilla/Opera ( set in HTTP/1.0 mode ) are sending a Host: header. Some don't include the port if the port is 80, but include it if it's not. ( at least that's what I remember ) I would rather enforce what the browsers are doing, not watchdog :-) I think Nacho has a valid point - using the port from socket ( when a Host header is present ) works fine unless a redirection is done by some hardware/ipchain/tcpmon/etc. This redirection is not that uncommon ( especially if you don't want to run tomcat directly on 80 for some reasons ) If we don't have a Host header - socket is the only choice and we should use it. But if a Host: is present, I would rather fix watchdog to do what the browsers are doing. ( of course, that would require someone to actually verify what are the browsers sending - and I won't do it, Character-Set hunting was more then enough for me... ) Costin -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>