Francois-Rene Rideau wrote:
The bug symptoms are that (1) when a request to a ProxyPass host contains %3A, the %3A is expanded to a colon, which yields an incorrect HTTP URL that confuses the remote host. (2) when a request to a ProxyPass host contains %2F, apache rejects the request with a 404 without even contacting the remote host.
In theory the proxy should pass the URL as is to the backend server, without any canonicalisation at all.
Can anyone see any reason why a proxy request should have the URL changed?
Regards, Graham --
