Re: Re: Tomcat 4.1.30 HTTP-HTTPS redirect problem (second attempt)
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 attempt) 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 Stewart [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] 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 work fine. When I move from an unsecure to a secure area of my application, the dialog box pops up and upon entering the correct user/password, I'm redirected to the secure port. However, if I change to form based authentication, when trying to send me to the login form, it sends me to the unsecure port using https. In other words: https://localhost:8080/secureApp/login.jsp It should be sending me to 8081. Any clue why this would happen? Snippets from my connectors in server.xml are below. If you need other info, just ask. Connector className=org.apache.coyote.tomcat4.CoyoteConnector ... port=8080 ... redirectPort=8081 scheme=http secure=false ... Factory className=org.apache.catalina.net.DefaultServerSocketFactory/ /Connector Connector className=org.apache.coyote.tomcat4.CoyoteConnector ... port=8009 ... redirectPort=8081 scheme=http secure=false ... Factory className=org.apache.catalina.net.DefaultServerSocketFactory/ /Connector Connector className=org.apache.catalina.connector.http.HttpConnector port=8081 ... scheme=https secure=true Factory className=org.apache.catalina.net.SSLServerSocketFactory clientAuth=false keystoreFile=.keystore protocol=TLS/ /Connector ___ Check-out GO.com GO get your free GO E-Mail account with expanded storage of 6 MB! http://mail.go.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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. Valentin mailto: [EMAIL PROTECTED] From: Ryan Stewart [EMAIL PROTECTED] Reply-To: Tomcat Users List [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Tomcat 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 application development, and the problem is related to that. Using basic authentication, things work fine. When I move from an unsecure to a secure area of my application, the dialog box pops up and upon entering the correct user/password, I'm redirected to the secure port. However, if I change to form based authentication, when trying to send me to the login form, it sends me to the unsecure port using https. In other words: https://localhost:8080/secureApp/login.jsp It should be sending me to 8081. Any clue why this would happen? Snippets from my connectors in server.xml are below. If you need other info, just ask. Connector className=org.apache.coyote.tomcat4.CoyoteConnector ... port=8080 ... redirectPort=8081 scheme=http secure=false ... Factory className=org.apache.catalina.net.DefaultServerSocketFactory/ /Connector Connector className=org.apache.coyote.tomcat4.CoyoteConnector ... port=8009 ... redirectPort=8081 scheme=http secure=false ... Factory className=org.apache.catalina.net.DefaultServerSocketFactory/ /Connector Connector className=org.apache.catalina.connector.http.HttpConnector port=8081 ... scheme=https secure=true Factory className=org.apache.catalina.net.SSLServerSocketFactory clientAuth=false keystoreFile=.keystore protocol=TLS/ /Connector ___ Check-out GO.com GO get your free GO E-Mail account with expanded storage of 6 MB! http://mail.go.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] _ Watch the online reality show Mixed Messages with a friend and enter to win a trip to NY http://www.msnmessenger-download.click-url.com/go/onm00200497ave/direct/01/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Re: Tomcat 4.1.30 HTTP-HTTPS redirect problem (second attempt)
No, you misunderstand. Port 8080 is the unsecure port, so trying to access it with https gives a cannot find server error. That's my problem. For some reason, the server is trying to redirect to an unsecure port using a secure protocol, which doesn't work. -Original Message- From: 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. Valentin mailto: [EMAIL PROTECTED] From: Ryan Stewart [EMAIL PROTECTED] Reply-To: Tomcat Users List [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Tomcat 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 application development, and the problem is related to that. Using basic authentication, things work fine. When I move from an unsecure to a secure area of my application, the dialog box pops up and upon entering the correct user/password, I'm redirected to the secure port. However, if I change to form based authentication, when trying to send me to the login form, it sends me to the unsecure port using https. In other words: https://localhost:8080/secureApp/login.jsp It should be sending me to 8081. Any clue why this would happen? Snippets from my connectors in server.xml are below. If you need other info, just ask. Connector className=org.apache.coyote.tomcat4.CoyoteConnector ... port=8080 ... redirectPort=8081 scheme=http secure=false ... Factory className=org.apache.catalina.net.DefaultServerSocketFactory/ /Connector Connector className=org.apache.coyote.tomcat4.CoyoteConnector ... port=8009 ... redirectPort=8081 scheme=http secure=false ... Factory className=org.apache.catalina.net.DefaultServerSocketFactory/ /Connector Connector className=org.apache.catalina.connector.http.HttpConnector port=8081 ... scheme=https secure=true Factory className=org.apache.catalina.net.SSLServerSocketFactory clientAuth=false keystoreFile=.keystore protocol=TLS/ /Connector ___ Check-out GO.com GO get your free GO E-Mail account with expanded storage of 6 MB! http://mail.go.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat 4.1.30 HTTP-HTTPS redirect problem (second attempt)
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 Stewart [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] 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 work fine. When I move from an unsecure to a secure area of my application, the dialog box pops up and upon entering the correct user/password, I'm redirected to the secure port. However, if I change to form based authentication, when trying to send me to the login form, it sends me to the unsecure port using https. In other words: https://localhost:8080/secureApp/login.jsp It should be sending me to 8081. Any clue why this would happen? Snippets from my connectors in server.xml are below. If you need other info, just ask. Connector className=org.apache.coyote.tomcat4.CoyoteConnector ... port=8080 ... redirectPort=8081 scheme=http secure=false ... Factory className=org.apache.catalina.net.DefaultServerSocketFactory/ /Connector Connector className=org.apache.coyote.tomcat4.CoyoteConnector ... port=8009 ... redirectPort=8081 scheme=http secure=false ... Factory className=org.apache.catalina.net.DefaultServerSocketFactory/ /Connector Connector className=org.apache.catalina.connector.http.HttpConnector port=8081 ... scheme=https secure=true Factory className=org.apache.catalina.net.SSLServerSocketFactory clientAuth=false keystoreFile=.keystore protocol=TLS/ /Connector ___ Check-out GO.com GO get your free GO E-Mail account with expanded storage of 6 MB! http://mail.go.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
