The AJP/1.3 Connector uses the scheme that is sent from IIS/Httpd/SunOne. The scheme and isSecure on the <Connector ./> is ignored.
I suppose that it wouldn't be too hard to add a believeMe="true" attribute to the <Connector> tag to handle your case. If you feel strongly about it, open a BZ enhancement request. Of course, if you include a patch, it will likely get looked at sooner ;-). Otherwise, a simple and obvious hack to o.a.c.connector.CoyoteAdapter.postParseRequest will give you a custom version of Tomcat that does what you want. "Earnie Dyke" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] Greetings all, We have the following AJP connector configuration: <!-- A AJP 1.3 Connector on port 8009 --> <Connector port="8009" address="${jboss.bind.address}" enableLookups="false" redirectPort="8443" debug="6" protocol="AJP/1.3" scheme="https" isSecure="true"/> I expected that when my application does a request.getScheme() I will get back HTTPS but I am not, I get HTTP. Do I not understand the purpose of scheme=? The problem we are trying to solve is this: 1. Loadbalancer receives HTTPS request, terminates SSL and forwards HTTP request to IIS server 2. IIS Server, using ISAPI Redirector, forwards request to JBoss/AJP Connector 3. When a Struts action is configured as a redirect the url returned to the browser is HTTP not HTTPS. Any help solving this would be greatly appreciated. Earnie! Earnest Dyke IS Technical Designer The Virginia Retirement System Richmond, Va 804-649-8059 ext 359 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
