httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mike Cardwell <>
Subject Re: [users@httpd] Re: mod_proxy doesn't proxy with %2F
Date Wed, 07 Mar 2007 16:39:46 GMT
* on the Wed, Mar 07, 2007 at 02:48:16PM +0000, Mike Cardwell wrote:

> This was on the dev list. I've brought it onto the users list as I no
> longer think it's a bug as such. Please see my original email above, and
> my update below for the issue.
> Right. I've made a *little* progress. Reading the core docs I found:
> "The AllowEncodedSlashes directive allows URLs which contain encoded path
> separators (%2F for /  and additionally %5C for \ on according systems)
> to be used. Normally such URLs are refused with a 404 (Not found)
> error."
> So these requests are being 404'd simply for containing %2F's in the
> path. When I turn on encoded slashes with:
> AllowEncodedSlashes On
> It starts to proxy. But it starts to proxy the wrong thing
> Requests for:
> https://the.domain/session/session_id/MessagePart/INBOX%2FArchive/message_id/filename.txt
> Get proxied to:
> I need it to be proxied to:
> Where do I go from here?

I've sorted this now. Using a combination of AllowEncodedSlashes,
mod_rewrite and an external script called as a RewriteMap to change /'s
to %2F's. A horrible, unholy hack, but it works.


The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:> for more info.
To unsubscribe, e-mail:
   "   from the digest:
For additional commands, e-mail:

View raw message