You can just use proxy_pass_ajp instead just proxy_pass. This way you
don't need tomcat ssl listener.
Rainer Jung wrote:
Doctor Khumalo schrieb:
OK, thanks.
If I remove Tomcat from the equation, I can get HTTPS to work with
Apache but when I try to start Tomcat and proxy the HTTPS request to
Tomcat, it fails. So, enabling HTTPS on Tomcat 8443 like the
following still fails:
<Connector port="8443" minSpareThreads="5"
maxSpareThreads="75" proxyName="local3"
enableLookups="true" disableUploadTimeout="true"
acceptCount="100" maxThreads="200" scheme="https"
secure="true" SSLEnabled="true"
SSLCertificateFile="/usr/local/apache2/conf/ssl.key/local3.crt"
SSLCertificateKeyFile="/usr/local/apache2/conf/ssl.key/server.key"
clientAuth="false" sslProtocol="TLS"/>
Can you talk to Tomcat port 8443 using HTTPS directly with your browser?
As long as that doesn't work, the combination with Apache in front will
not do it as well.
Is the encryption between Apache and Tomcat important for you? If no,
then don't bother setting up an https port and instead use http between
Apache and Tomcat.
Regards,
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Milan Cvejić
Sistem Administrator
Inbox d.o.o.
Software for Internet
Bulevar Zorana Đinđića 99, 11000 Beograd, Srbija
tel +381 11 313 07 21
mob +381 65 344 42 23
fax +381 11 313 37 34
[EMAIL PROTECTED]
www.inbox-online.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
