Re: Tomcat 5.5 and secure="true"

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear Filip, Thanks for the info! This was what I was planning on doing with Tomcat 5.5. I have now gone back to use mod_proxy_ajp. (I can not migrate to Tomcat 6.0 for political reasons)... Regards Andrew On 29/03/2007, at 9:54 PM, Filip Hanik

Re: Tomcat 5.5 and secure="true"

With tomcat 6, you could do this: 1. For non SSL traffic Just ProxyPass to tomcat like always (set ProxyPreserveHost On) 2. For SSL traffic Proxy pass to another connector setup like this SSLEnabled=false, means it is http, not https, but request.getScheme - will return https request.isSec

Re: Tomcat 5.5 and secure="true"

Andrew Miehs wrote: After reading all the comments regarding mod_proxy_ajp, I am currently looking at migrating to mod_proxy_http. The application uses "isSecure" to check whether the request is an HTTPS connection or not. But you obviously didn't read all the comments. You will need to

Tomcat 5.5 and secure="true"

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear List, After reading all the comments regarding mod_proxy_ajp, I am currently looking at migrating to mod_proxy_http. The application uses "isSecure" to check whether the request is an HTTPS connection or not. Therefore, I have created 2