DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8174>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8174
Using mod_proxy reverse proxy with mod_ssl causes hang
Summary: Using mod_proxy reverse proxy with mod_ssl causes hang
Product: Apache httpd-2.0
Version: 2.0.35
Platform: Sun
OS/Version: Solaris
Status: NEW
Severity: Normal
Priority: Other
Component: mod_proxy
AssignedTo: bugs@httpd.apache.org
ReportedBy: georgeh@frictionless.com
Not sure if this is operator error or a bug, but it appears to be a bug.
Under 1.3, using ProxyPass and ProxyReverse within an SSL VirtualHost, one could
add an SSL front-end to a second server that may not support SSL. This
configuration doesn't seem to work under 2.0.35.
On my configuration, SSL virtual hosts work fine, and both forward and reverse
proxy virtual hosts work fine when they are not SSL. An SSL virtual host with a
reverse proxy, however, connects (verified using openssl's s_client command),
but never responds. Commenting out the reverse proxy lines on that exact virtual
host causes the default apache HTML pages to come up, so the SSL isn't the problem.
Also, the remote server does see the socket opened by the proxy, but does not
receive any data. (Verified by pointing the reverse proxy at a dummy Java http
server -- proxy connects, no data comes through)
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8174>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8174
Using mod_proxy reverse proxy with mod_ssl causes hang
Summary: Using mod_proxy reverse proxy with mod_ssl causes hang
Product: Apache httpd-2.0
Version: 2.0.35
Platform: Sun
OS/Version: Solaris
Status: NEW
Severity: Normal
Priority: Other
Component: mod_proxy
AssignedTo: bugs@httpd.apache.org
ReportedBy: georgeh@frictionless.com
Not sure if this is operator error or a bug, but it appears to be a bug.
Under 1.3, using ProxyPass and ProxyReverse within an SSL VirtualHost, one could
add an SSL front-end to a second server that may not support SSL. This
configuration doesn't seem to work under 2.0.35.
On my configuration, SSL virtual hosts work fine, and both forward and reverse
proxy virtual hosts work fine when they are not SSL. An SSL virtual host with a
reverse proxy, however, connects (verified using openssl's s_client command),
but never responds. Commenting out the reverse proxy lines on that exact virtual
host causes the default apache HTML pages to come up, so the SSL isn't the problem.
Also, the remote server does see the socket opened by the proxy, but does not
receive any data. (Verified by pointing the reverse proxy at a dummy Java http
server -- proxy connects, no data comes through)