Hi Christian,
thanks for your feedback. Good to know the reason and that the theory
works, at least if SSL is explicitely activated in the vhost.
mod_jk gets the ssl info froom an apache httpd internal environment
variable. It looks like this wasn't set by your configuration. In case
one offloads ssl to an appliance, one can still configure mod_jk inside
Apache to think it's SSL.
Regards,
Rainer
Christian Andersson wrote:
Hi Rainer, and thanks for trying to help me.
I had been trying most of what you wrote, and it still looked like it
was tomcat, but there was one thing that "struck me" while doing all
these tests/changes
"mod_jk transfers the knowledge of the hostname and port used in Apache
htpd to the AJP connector, so that self referring URLs can be produced
correctly."
Comparing my virtualhost definition
<VirtualHost *:443>
ServerName demo.mydomain
JkMount /* worker1
</VirtualHost>
with one provided with the installation for squirrelmail (php based)
I did some changes to my virtualhost....
<IfModule mod_ssl.c>
<VirtualHost *:443>
ServerName demo.mydomain
JkMount /* worker1
SSLEngine on
SSLProtocol all -SSLv2
SSLCipherSuite ALL:!ADH:!EXPORT:!SSLv2:RC4+RSA:+HIGH:+MEDIUM:+LOW
SSLCertificateFile /etc/pki/tls/certs/localhost.crt
SSLCertificateKeyFile /etc/pki/tls/private/localhost.key
</VirtualHost>
</IfModule>
and Voila, now it works...
apparently https WAS working without all of this SSL parameters, but
mod_jk sent the wrong information to the server.
so even if your suggestions on what to check did not leave me to an
answer, your message still helped :-)
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
