or something. I think that's why the servlet spec says the
uri is absolute.
Of course, an intelligent client would know how to handle both ;)
a NAT handle traffic at a lower level, ca not be able of change part of
the packet transmited, perhaps with apache's reverse proxying it's
Excuse my ignorance, Why tomcat 3.x makes redirects (302) absolute ?
It leads to problems with NAT ( at router level ) redirects, and reverse
proxys, and it can commented without aparent harm
Saludos ,
Ignacio J. Ortega
Nacho wrote:
Excuse my ignorance, Why tomcat 3.x makes redirects (302) absolute ?
It leads to problems with NAT ( at router level ) redirects, and reverse
proxys, and it can commented without aparent harm
See servlet 2.2 specification, section 6.3, first complete paragraph.
Making
Hola Craig:
See servlet 2.2 specification, section 6.3, first complete paragraph.
Making the URL absolute is required.
It's required when it's used trought the convenience methods
(sendRedirect sendError) not when the container send itself a
redirect... and this was the reasoning behind
Ohh unpleasure findings ( and i do need to read the damn RFC too :-)
Tomcat 3.2 seems to have another bug!!!
i've obtained this ( by means of telnet ) from different http servers,
after done a GET / in all of them, i obtained
This is from IIS 5.0
first finding: How IIS makes this work
Nacho wrote:
Ohh unpleasure findings ( and i do need to read the damn RFC too :-)
Tomcat 3.2 seems to have another bug!!!
i've obtained this ( by means of telnet ) from different http servers,
after done a GET / in all of them, i obtained
This is from IIS 5.0
first finding: How
- Original Message -
From: "Nacho" [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Saturday, November 04, 2000 9:32 PM
Subject: RE: Why tomcat 3.x makes redirects (302) absolute ?
Hola Craig:
The fact that other servers break the rules is no excuse for
Tomcat
