DO NOT REPLY [Bug 34602] - mod_rewrite fails to correctly deal with URLS that have escapes in them

[bu...@apache.org]

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=34602>.
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=34602





------- Additional Comments From jonathan@dnil.net  2007-10-17 12:57 -------
I'm not sure if people are succesfully convincing other people this IS a bug.
Let's take another example:

Incoming URL:
/foo?bar=%3Abaz

This is a perfectly legal URL right? The "%3A" is a perfectly legally encoded
"/" char---that is the way it OUGHT to be included. 

Now let's say I want to redirect all /foo urls to an external server:

RewriteRule /foo http://somewhere.else.com/other [R]

Expected behavior, redirect to:
http://somewhere.else.com/other?bar=%3Abaz

Yes?

ACTUAL behavior, redirect to:
http://somewhere.else.com/other?bar=%253Abaz

Some of you are arguing that this is intended behavior? How can this possibly
be? I got a perfectly legal URL in with a perfectly legal query string. My
RewriteRule should be expected to leave the query string exacty intact, right?
Yet it corrupts it to mean something else. 

To me, this is obviously a bug. [And one that's causing me a serious probelm at
the moment to boot]. 

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org