https://issues.apache.org/bugzilla/show_bug.cgi?id=47379
Summary: Reverse proxy configuration does handle HTTP CONNECT
requests correctly
Product: Apache httpd-2
Version: 2.2.9
Platform: PC
OS/Version: All
Status: NEW
Keywords: RFC
Severity: normal
Priority: P2
Component: mod_proxy
AssignedTo: [email protected]
ReportedBy: [email protected]
Setting up a reverse proxy with:
LoadModule proxy_module modules/mod_proxy.so
LoadModule proxy_http_module modules/mod_proxy_http.so
LoadModule proxy_connect_module modules/mod_proxy_connect.so
Listen 9006
NameVirtualHost *:9006
<VirtualHost *:9006>
AllowCONNECT 3030
ProxyPass / xxx.xxx.xxx.xxx:3030
ProxyPassReverse / xxx.xxx.xxx.xxx:3030
</VirtualHost>
does not work, since the ProxyPass directive throws the error: "ProxyPass URL
must be absolute!"
Changing the URL to
ProxyPass / http://xxx.xxx.xxx.xxx:3030
makes Apache start, but HTTP CONNECT requests are forwarded to the next
endpoint.
Unless i have not misinterpreted the HTTP 1.1 spec, it should not forward a
HTTP request to the endpoint when a CONNECT request was received. It should
rather create a tunnel and return CONNECTION ESTABLISHED to the initial caller
so that the caller and the endpoint can talk a custom protocol tunneled through
the reverse proxy.
This worked fine with Apache 2.0.x and works fine with a simple forward proxy.
Unfortunately it is broken for reverse proxies.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
