You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bugs@httpd.apache.org by bu...@apache.org on 2019/10/02 13:32:51 UTC
[Bug 63437] MergeSlashes option breaks protocol specifier in URIs
https://bz.apache.org/bugzilla/show_bug.cgi?id=63437
--- Comment #8 from Thomas Jarosch <th...@intra2net.com> ---
I looked around our module's git history and we're using r->uri since 2003
without any issue in this "proxy filter" module chained after mod_proxy_http.
The forward proxy is running in an own instance these days, so it was easy for
us to configure MergeSlashes to OFF without any bad side effects. So we have a
working workaround.
The question is: Is it worth fixing to turn the r->uri field into a proper URI
again?
Could the MergeSlashes code be changed into skipping any protocol identifier
like http:// ftp:// xyz:// in the beginning of an URI? Or would this just be
half of a solution since further slashes in URLs still get merged?
I'm just afraid that other modules might also be affected. A few other places
in the proxy code make use of r->uri, so they would need to be inspected:
* mod_proxy_balancer.c
* error logging in mod_proxy_http.c
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org