httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chris Arnold <carn...@electrichendrix.com>
Subject [users@httpd] 502 Bad Gateway
Date Tue, 26 Feb 2013 01:06:34 GMT
Apache 2.2.12 on SLES11. I have an app that runs on tomcat port 8080. I have bee following:
http://tomcat.apache.org/tomcat-6.0-doc/proxy-howto.html

I want people to get to this app by typing https://domain/app. To achieve this, i have used
proxypass (reverse) in the SSL vhost:

ProxyPass /app https://192.168.123.3:8080/app
ProxyPassReverse /app https://192.168.123.3:8080/app

Here is part of the Tomcat connector config:
<Connector port="8080" URIEncoding="UTF-8" protocol="HTTP/1.1"
               proxyName="teknerds.net"
               proxyPort="80"
               connectionTimeout="20000"
               redirectPort="8443" />

Here is the Log the apache proxy:

[Mon Feb 25 19:16:06 2013] [error] (502)Unknown error 502: proxy: pass request body failed
to 192.168.123.3:8080 (192.168.123.3)
[Mon Feb 25 19:16:06 2013] [error] proxy: pass request body failed to 192.168.123.3:8080 (192.168.123.3)
from 75.177.185.93 ()

If i put the proxypass statements into the non-SSL vhost, this works fine. Although i can
not find it now, i read on the apache/tomcat page that you do not need tomcat configured for
SSL in this type of setup but it seems to me that that may be the problem. The reasoning went
something like this:
even if you have the front end encrypted, the frontend will communicate unencrypted with the
backend (tomcat) and the reply back to the client browser will be sent out encrypted.

2 questions:
will the way i am trying to configure work?
do i need to use mod_jk?

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org


Mime
View raw message