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 2004/07/06 18:38:39 UTC
DO NOT REPLY [Bug 11265] -
mod_rewrite fails to encode special characters
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=11265>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=11265
mod_rewrite fails to encode special characters
------- Additional Comments From app@pobox.com 2004-07-06 16:38 -------
This appears to be similar to the 2.0 bug, #15207. Is this a red herring, or
could the approach used in that patch (which has already been accepted) be
relevant here as well?
Confirming that this issue still exists in 1.3.31, RHL 7.5.
.htaccess for secure.example.com:
> ProxyPass /NetStorage/ https://otherserver.example.com/NetStorage/
> ProxyPass /oneNet/ https://otherserver.example.com/oneNet/
request for:
https://secure.example.com/oneNet/NetStorage/DriveI%40VOL/Shared%20Projects
gets a 400 Bad Request from otherserver.example.com because the %20 was
expanded to a space. (otherserver reports "The request line contained invalid
characters following the protocol string", as well it should.)
best,
-arthur.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org