It's not just Tomcat, every web server does that (from what I've
seen). I would guess it's required by the HTTP spec.
--
Len Popp
[EMAIL PROTECTED]
http://www.lmp.dyndns.org/
On 10/21/06, Ramez Ghazzaoui <[EMAIL PROTECTED]> wrote:
Nice observation, champ!
I still don't understand why Tomcat feel
Nice observation, champ!
I still don't understand why Tomcat feels the need to send the 302
resubmit request when in fact it knows exactly what the browser's
request is.
Cheers,
-Ramez
Len Popp wrote:
Note that this problem only happens with port 443. With any other
port, IE6 correctly redire
Note that this problem only happens with port 443. With any other
port, IE6 correctly redirects on the same port. Port 443 is usually
used for HTTPS - for some reason IE6 thinks it should redirect to port
80 in this special case. So, if you're able to use a port other than
443 the missing-/ URLs w
So the problem's origin is my unusual port assignment.
Thank you Chuck. Case closed :-)
-Ramez
Caldarale, Charles R wrote:
From: Ramez Ghazzaoui [mailto:[EMAIL PROTECTED]
Subject: Re: Eliminating the need for a trailing slash in
accessing sub-directoryresourceson a Tomcat HTTP server
I was de
> From: Ramez Ghazzaoui [mailto:[EMAIL PROTECTED]
> Subject: Re: Eliminating the need for a trailing slash in
> accessing sub-directoryresourceson a Tomcat HTTP server
>
> I was definitely not experiencing a 302 or automatic
> refresh/resubmit.
Actually, you are, regardless of browser. Crank
