Re: [EMAIL PROTECTED] mod_rewrite decodes %20 - 400 bad request

2005-11-21 Thread ogjunk-httpd1
Hi, To wrap up this thread and for the archives: Changing from [P] to [PT] also solved the issue with %20 being decoded to a space before dispatching the request to the rewritten URL (what the subject describes). Consequently, this now works beautifully:

Re: [EMAIL PROTECTED] mod_rewrite decodes %20 - 400 bad request

2005-11-21 Thread Robert Ionescu
[EMAIL PROTECTED] wrote: Changing from [P] to [PT] also solved the issue with %20 being decoded to a space before dispatching the request to the rewritten URL (what the subject describes). Because no ProxyPass is used anymore, but it was/is a bug:

Re: [EMAIL PROTECTED] mod_rewrite decodes %20 - 400 bad request

2005-11-20 Thread ogjunk-httpd1
Hi, --- Robert Ionescu [EMAIL PROTECTED] wrote: [EMAIL PROTECTED] wrote: One more thing --- André Malo [EMAIL PROTECTED] wrote: * [EMAIL PROTECTED] wrote: Hi, I solved this problem by substituting %20 with + characters. Apparently, mod_rewrite doesn't convert + to

Re: [EMAIL PROTECTED] mod_rewrite decodes %20 - 400 bad request

2005-11-15 Thread ogjunk-httpd1
Hello André, --- André Malo [EMAIL PROTECTED] wrote: * [EMAIL PROTECTED] wrote: Hi, I solved this problem by substituting %20 with + characters. Apparently, mod_rewrite doesn't convert + to spaces as it does with %20. Your problem is home-made. mod_rewrite always works on the

Re: [EMAIL PROTECTED] mod_rewrite decodes %20 - 400 bad request

2005-11-15 Thread ogjunk-httpd1
One more thing --- André Malo [EMAIL PROTECTED] wrote: * [EMAIL PROTECTED] wrote: Hi, I solved this problem by substituting %20 with + characters. Apparently, mod_rewrite doesn't convert + to spaces as it does with %20. Your problem is home-made. mod_rewrite always works

Re: [EMAIL PROTECTED] mod_rewrite decodes %20 - 400 bad request

2005-11-15 Thread Robert Ionescu
[EMAIL PROTECTED] wrote: One more thing --- André Malo [EMAIL PROTECTED] wrote: * [EMAIL PROTECTED] wrote: Hi, I solved this problem by substituting %20 with + characters. Apparently, mod_rewrite doesn't convert + to spaces as it does with %20. Your problem is home-made.

Re: [EMAIL PROTECTED] mod_rewrite decodes %20 - 400 bad request

2005-11-14 Thread ogjunk-httpd1
Hi, I solved this problem by substituting %20 with + characters. Apparently, mod_rewrite doesn't convert + to spaces as it does with %20. I say solved, as this is a hack, and I hate hacks... :( Is there a list/forum/anything focused on Apache modules or mod_rewrite in particular? Thanks, Otis

Re: [EMAIL PROTECTED] mod_rewrite decodes %20 - 400 bad request

2005-11-14 Thread André Malo
* [EMAIL PROTECTED] wrote: Hi, I solved this problem by substituting %20 with + characters. Apparently, mod_rewrite doesn't convert + to spaces as it does with %20. Your problem is home-made. mod_rewrite always works on the unescaped URI-path and you're explicitly specifying by using [NE]

[EMAIL PROTECTED] mod_rewrite decodes %20 - 400 bad request

2005-11-12 Thread ogjunk-httpd1
Hello, I'm using mod_rewrite with httpd 1.3.34 and am having some difficulties with it when the URL that is getting rewritten has spaces (encoded as %20) in it. Example: http://simpy.com/user/otis/search/foo%20bar The error I get is 400 bad Request: Bad Request Your browser sent a request