https://issues.apache.org/bugzilla/show_bug.cgi?id=55892
Bug ID: 55892
Summary: ProxyRemote with HTTPS backend sends requests with
absoluteURI instead of abs_path
Product: Apache httpd-2
Version: 2.5-HEAD
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P2
Component: mod_proxy
Assignee: [email protected]
Reporter: [email protected]
With ProxyRemote configuration the HTTPS backend receives a request with an
absoluteURI - which the backend couldn't handle.
Example:
> ServerName myserver.localnet
> ProxyRemote https://foobar.com http://forwardproxy.localnet:8080
> ProxyPass /content/ https://foobar.com/content/
The Request
https://myserver.localnet/content/index.html
will be received and logged by myserver.localnet as
"GET /content/index.html HTTP/1.1"
After a successfull CONNECT handshake with the forwardproxy.localnet we get a
SSL tunnel to the backend server. Cause of the SSL tunnel the request won't be
transformed/touched by the forward proxy. But the proxy module always sends
requests in the absoluteURI form to the backend if a forward proxy is
configured. So the backend receives the request in the absoluteURI form:
"GET https://foobar.com/content/indext.html HTTP/1.1"
RFC 2616 5.1.2 says that the absoluteURI form should be supported by every
HTTP/1.1 Server. My backend seems to have an incomplete rfc implemetation here.
:-(
Setting the environment "force-proxy-request-1.0" doesn't help.
I'm not sure about the severity. Is it a bug or a feature to handle improper
backend server. ;-)
--
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]
