Re: Re: Tomcat 4.1.30 HTTP-HTTPS redirect problem (second attempt)

2004-06-06 Thread Ryan Stewart
Ah, thanks! I'll have to go with option 2 as I'm pretty well tied to Tomcat 4 and I have to develop toward IE. -Original Message- From: Bill Barker[EMAIL PROTECTED] To: [EMAIL PROTECTED] Date: Sat Jun 05 21:47:40 PDT 2004 Subject: Re: Tomcat 4.1.30 HTTP-HTTPS redirect problem (second

RE: Tomcat 4.1.30 HTTP-HTTPS redirect problem (second attempt)

2004-06-05 Thread Ariel Valentin
What is happening once you are logged in? Does it continue to use the secure protocol on port 8080? https://localhost:8080/ Mr. Ariel S. Valentin mailto: [EMAIL PROTECTED] From: Ryan Stewart [EMAIL PROTECTED] Reply-To: Tomcat Users List [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Tomcat

Re: Re: Tomcat 4.1.30 HTTP-HTTPS redirect problem (second attempt)

2004-06-05 Thread Ryan Stewart
: Ariel Valentin[EMAIL PROTECTED] To: [EMAIL PROTECTED] Date: Sat Jun 05 19:01:31 PDT 2004 Subject: Re: Tomcat 4.1.30 HTTP-HTTPS redirect problem (second attempt) What is happening once you are logged in? Does it continue to use the secure protocol on port 8080? https://localhost:8080/ Mr. Ariel S

Re: Tomcat 4.1.30 HTTP-HTTPS redirect problem (second attempt)

2004-06-05 Thread Bill Barker
This is a pretty well known bug in MSIE. The short version is that that TC 4.1.x sends two redirects to get you to the login page, and MSIE gets confused. The options to get around this are: 1) Don't use MSIE. 2) Use the default SSL port (e.g. 443). 3) Use TC 5.0.x instead of TC 4.1.x. Ryan