Greetings, I have a server running Apache 1.3.22 and Tomcat 3.3 on Solaris 8. Up until now my Tomcat configuration included just one webapp and it used the standard port 443 for SSL (through Apache). That all works really well.
Now I am trying to integrate a second webapp, and therefore a second context that will use a different SSL certificate. This is no problem for all http requests since they all use port 80, but https ports are a different story. Since 443 is already used for the first context, I am forced to use a different port for the second, and to include it in my URL (i.e. https://www.xxx.com:444/). That too works fine now that I got it set up correctly in my Apache configuration file. So here's the problem: The client will surf through the site and collect his set of session objects (cart, etc.), but when it comes to to activate the SSL, Tomcat seems to look at that URL as if it were a new user, therefore assigning it a new session. The client looses his cart. Any ideas of how I can make Tomcat not pay attention to the port for the server information? any help would be a blessing Michael Welsh -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
