* 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: > > https://127.0.0.1:9100/session/session_id/MessagePart/INBOX/Archive/message_id/filename.txt > > I need it to be proxied to: > > https://127.0.0.1:9100/session/session_id/MessagePart/INBOX%2FArchive/message_id/filename.txt > > 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. Mike --------------------------------------------------------------------- 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: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|