The story is that the receiving application is processing the request as:
http://<server>/<attribute1>/<attribute2>/<attribute3>
so if I want a literal '/' in one of those attributes it has to be encoded otherwise the request processing doesn't break things up properly.
with LogLevel up to info, I get this in the apache error log:
[Wed Jun 28 10:44:32 2006] [info] [client 192.168.1.10] found %2f (encoded '/') in URI (decoded='/c/wiki/new/this/that'), returning 404
so it seems that this is intentional behavior and probably not a bug persay. I may have to redesign the application..
thanks for all your help.
On 6/28/06,
Axel-Stéphane SMORGRAV <[EMAIL PROTECTED]> wrote:
What I did notice though, is that replacing the %2F with / did work. What's the story about this %2F ?
Unfortunately I'll have to pass on this one. If no-one else replies, you could do a test using Apache 2.2.2, and possibly file a bug report. You may have more luck filing a bug report after having tested against Apache 2.2.2 since the development effort is targeted at that version.
-ascs
________________________________
From: [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED]] On Behalf Of Lewis Hoffman
Sent: Wednesday, June 28, 2006 6:10 PM
To: users@httpd.apache.org
Subject: Re: [EMAIL PROTECTED] reverse proxy fails on uri escape sequences
No attachment to a rewrite rule. Unfortunately, changing to a simple proxy pass yields exactly the same behavior. It seems as if somethings going wrong higher up in the chain..
thanks for looking into this.
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL: http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: [EMAIL PROTECTED]
" from the digest: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Lewis Hoffman
Grass Commons
[EMAIL PROTECTED]
541-343-1944
