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 [EMAIL PROTECTED] 2007-03-21 11:06 ------- First: wow, I didn't know this bug was still open... (In reply to comment #19) > But you can process $_SERVER['REQUEST_URI'] within php or catch the variables > from the unprased ENV THE_REQUEST with a RewriteCond. Yeah, this is the method I went with in the end... and Mediawiki does the same thing for those that are curious. As for the correct behaviour... well, as has been mentioned, the rules for escaping are slightly different between the path and query part of the url. say you have RewriteRule ^(.*)$ pages/test.php?s=$1 [L] If you use the url /1&a=1 or /1%26a%3d1 the resulting internal url ends up as pages/test.php?s=1&a=1, in other words mod_rewrite is parsing the path part after it has been decoded, and then doing a direct copy into the query, without re-encoding it. So the question is, should mod_rewrite parse the urls before or after url decoding (maybe apache decodes before the url is passed to mod_rewrite?), and should it re-encode data when it is copied to the query, or leave that up to the script? -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
