the SSL Session-ID even if you are fronting with Apache
> (Apache passes it to Tomcat). However, be warned that this is a
> Tomcat-specific feature: It won't work if you try and port your app to
> another Servlet Container.
Thanks for warning...
Bye,
Mike
--
Michael Decke
cause HTTP is stateless.
That was the reason of creating session handled with cookies, URL
parameters, referrers etc.
You was a great help.
Thanks a lot!
Michael
--
Michael Decker [EMAIL PROTECTED]
TESIS SYSware Gmb
Okay, yes. That is a possibility, the application will offers, but it's
not forced to configure that way.
Thanks a lot!
Michael
--
Michael Decker [EMAIL PROTECTED]
TESIS SYSware GmbH http://www.tesis.de
Baierbrunnerstr. 15 * 81379 Muenchen * Tel.
on
> the same machine I suggesting making Tomcat listen on 127.0.0.1:8007.
Yes, that is, what I'm going to do.
My problem is, that the application session (set by cookie or url
parameter) is not associated with the SSL session. And I hope, there is
an easy way to that.
Thanks a lo
0/mod/mod_proxy.html
[2] http://httpd.apache.org/docs/2.2/mod/mod_proxy_ajp.html
[3] http://tomcat.apache.org/faq/connectors.html#vs
[4] http://wiki.jboss.org/wiki/Wiki.jsp?page=ModJK_FAQ
[5] http://tomcat.apache.org/tomcat-3.3-doc/tomcat-ssl-howto.html
--
Michael Decker [EM
