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
4.1.30 HTTP-HTTPS redirect problem (second attempt)
Date: Fri, 4 Jun 2004 20:24:52 -0700 (PDT)
I posted a question about this about a week ago, but haven't seen any
reply.
I've set up Tomcat 4.1.30 for secure access via SSL. Unsecure port is 8080,
secure port is 8081. I use Tomcat for J2EE
: 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
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
I posted a question about this about a week ago, but haven't seen any reply.
I've set up Tomcat 4.1.30 for secure access via SSL. Unsecure port is 8080, secure
port is 8081. I use Tomcat for J2EE application development, and the problem is
related to that. Using basic authentication, things
