> The problem is with the port info present in the host header, that is
> lost, and subsituted by the local por used in the connection.
Got it. :-)
That could be bad in settings with port mapping (a common situation as soon
as a firewall is involved).
> > T32 does support HTTP/1.1 host name bas
>
> Sorry that I didn't got any time to further investigate this issue.
>
> I didn't understood what exact distinction you make here. But
The problem is with the port info present in the host header, that is
lost, and subsituted by the local por used in the connection.. The patch
only corrects
> The problem, i think i'd found, is that when tomcat does a redirection
> do not use the "host" header received, he tries to recontruct host+port
> info based on his own port and the name (or ip ) found in the Host
> header of the request
Sorry that I didn't got any time to further investigate
Nacho wrote:
> Hola a todos:
>
> After some more research in the issues related to NATs and tomcat
> standalone, and more reading, i think i have found a real and common
> problem in tomcat 3.X, that it's not present in Tomcat 4.0 ( this is
> from a brief reading of the code ).
>
> The problem, i
