mod_ssl and mod_jk (Win32)

Environment:

Running Apache 2.0.43/OpenSSL 9.6.g as downloaded from
hunter.campbus.com and mod_jk 1.2.1 for build 2.0.43 from jakarta.

Problem:

When I access the URL https://localhost/app, I *hope* to get the
contents of index.html (i.e., https://localhost/app/index.html).
Instead, my browser (Mozilla 1.0) reports a "Bad Request" error,
indicating that there was a protocol error in accessing the URL
"http://localhost:443/app/index.html".

Of course there will be a protocol error -- using http to talk to the
https port!

Any ideas where that error might come from? I assume its something
happening with a redirect in Tomcat.

FWIW:

Each of the following URLs work fine (right now, I have Apache
configured to take all connections either from http or https and forward
to Tomcat):

+ http://localhost/app
+ http://localhost/app/index.html
+ https://localhost/app/index.html

Its only the https://localhost/app URL that's failing.

Thanks for any assistance,

Paul Christmann


____________________________________________________________ __________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List modssl-users@modssl.org
Automated List Manager majordomo@modssl.org

Re: mod_ssl and mod_jk (Win32)

Answering my own question in case anyone else ever encounters this:

Modify Tomcat's server.xml specifying scheme="https" (rather than
scheme="http") for the Connector used to wire Apache and Tomcat.

Paul Christmann wrote:
> Environment:
>
> Running Apache 2.0.43/OpenSSL 9.6.g as downloaded from
> hunter.campbus.com and mod_jk 1.2.1 for build 2.0.43 from jakarta.
>
> Problem:
>
> When I access the URL https://localhost/app, I *hope* to get the
> contents of index.html (i.e., https://localhost/app/index.html).
> Instead, my browser (Mozilla 1.0) reports a "Bad Request" error,
> indicating that there was a protocol error in accessing the URL
> "http://localhost:443/app/index.html".
>
> Of course there will be a protocol error -- using http to talk to the
> https port!
>
> Any ideas where that error might come from? I assume its something
> happening with a redirect in Tomcat.
>
> FWIW:
>
> Each of the following URLs work fine (right now, I have Apache
> configured to take all connections either from http or https and forward
> to Tomcat):
>
> + http://localhost/app
> + http://localhost/app/index.html
> + https://localhost/app/index.html
>
> Its only the https://localhost/app URL that's failing.
>
> Thanks for any assistance,
>
> Paul Christmann
>
>
> ____________________________________________________________ __________
> Apache Interface to OpenSSL (mod_ssl) www.modssl.org
> User Support Mailing List modssl-users@modssl.org
> Automated List Manager majordomo@modssl.org
>



____________________________________________________________ __________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List modssl-users@modssl.org
Automated List Manager majordomo@modssl.org