With tomcat 6, you could do this:
1. For non SSL traffic
Just ProxyPass to tomcat like always (set ProxyPreserveHost On)
<Connector protocol="org.apache.coyote.http11.Http11NioProtocol"
port="8080"
proxyPort="80">
2. For SSL traffic
Proxy pass to another connector setup like this
<Connector protocol="org.apache.coyote.http11.Http11NioProtocol"
secure="true" scheme="https"
SSLEnabled="false"
port="8081"
proxyPort="443">
SSLEnabled=false, means it is http, not https, but
request.getScheme - will return https
request.isSecure - will return true
request.getServerPort - will return 443
Do you need more?
Filip
Mladen Turk wrote:
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 set up the whole bunch of headers in Apache and
create your own Servlet filter in Tomcat to be able to use that.
Regards,
Mladen.
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
