Re: Eliminating the need for a trailing slash in accessing sub-directoryresourceson a Tomcat HTTP server

2006-10-23 Thread Martin Gainty
If I interpret this correctly you're saying if I go to https://www.whateveryoursiteis.com OR http://www.whateveryoursiteis.com:443 IE 6 browser intentionally (with no 301/302 HTTP events being sent from web server) redirects to port 80? M- This e-mail

RE: Eliminating the need for a trailing slash in accessing sub-directoryresourceson a Tomcat HTTP server

2006-10-23 Thread Caldarale, Charles R
From: Martin Gainty [mailto:[EMAIL PROTECTED] Subject: Re: Eliminating the need for a trailing slash in accessing sub-directoryresourceson a Tomcat HTTP server If I interpret this correctly you're saying if I go to https://www.whateveryoursiteis.com OR

Re: Eliminating the need for a trailing slash in accessing sub-directoryresourceson a Tomcat HTTP server

2006-10-23 Thread Ramez Ghazzaoui
No, Martin. I believe this is not exactly true. - There is no https involved in this discussion. We're talking http on port 443. - This case involves having a directory name at the end of the path, and excluding the trailing slash which results in a 302 from the server. - This problem

RE: Eliminating the need for a trailing slash in accessing sub-directoryresourceson a Tomcat HTTP server

2006-10-21 Thread Caldarale, Charles R
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 up

Re: Eliminating the need for a trailing slash in accessing sub-directoryresourceson a Tomcat HTTP server

2006-10-21 Thread Ramez Ghazzaoui
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

Re: Eliminating the need for a trailing slash in accessing sub-directoryresourceson a Tomcat HTTP server

2006-10-21 Thread Len Popp
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

Re: Eliminating the need for a trailing slash in accessing sub-directoryresourceson a Tomcat HTTP server

2006-10-21 Thread Ramez Ghazzaoui
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

Re: Eliminating the need for a trailing slash in accessing sub-directoryresourceson a Tomcat HTTP server

2006-10-21 Thread Len Popp
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 feels