Nathan, I have noticed the behavior you describe on a Struts application that I worked on. However, I was not sure of why the :443 was added until your post. I was thinking that it was the web server, perhaps not.
Anyway, one issue to watch out for is that Netscape considers these two URLs to be from different servers, and thus won't send the session cookie from one to the other: > https://hostname:443/webapp/page.jsp > https://hostname/webapp/page.jsp If you are having trouble with people getting redirected back to your login page after they login with Netscape, this issue might be the cause. One solution (that has the significant downside that you have to maintain the setting) is to set the cookie domain for your server. You usually set it to the fully qualified domain name of your web server. The details of how to do that depend on what app server you are using. -Max ----- Original Message ----- From: "Nathan Anderson" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, February 07, 2002 3:59 PM Subject: Re: SSL + URL rewriting problem > I have a bit more information if anyone is interested in helping me with this issue.. > > I found out that the HttpUtils.getRequestURL(). If I make a JSP with the following scriptlet: > > <%= HttpUtils.getRequestURL(request) %> > > I get this: > > http://hostname:443/webapp/page.jsp > > when the actual request URL was: > > https://hostname/webapp/page.jsp > > Any ideas appreciated. > > Nathan Anderson > -- > Sent via jApache.org > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>