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-08-23 16:38 ------- Some of the comments here seem to suggest that all this is the expected behavior. Well, I, for one, don't get it. Allow me to elaborate on my experience with this bug. On my site, I direct searches through /search/ followed by the search query, and then another trailing slash. The rule I use is RewriteRule ^search(/(.+))?/$ /index.php?page=search&query=$2 [L] This works fine for queries that don't contain a slash. If I were to search for "9/10", for example, the requested path would become /search/9%2F10/ Now, from the discussion here, I gather that that won't work. And indeed, double encoding fixes it. I hate that solution, personally, but, more importantly: 1. The error I get is a 404. First of all, the content of that error page has the %2F decoded to /, which I don't fully get. But the really weird thing is that my ErrorDocument 404 applies in all cases except this one--I get a standard black on white 404 page for some reason. 2. Since escaping is the problem, allegedly, it should work if I omit the query from the eventual URL, right? However, even the trivial RewriteRule ^search /index.php [L] fails to match /search/9%2F10/. I realize this is not a help forum, but I would sure appreciate some input. I'm sorry if this is a different bug, but it seemed related. -- 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]
