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=38448>. 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=38448 Summary: mod_proxy encodes ~ to %7E in Reverse Proxy mode Product: Apache httpd-2 Version: 2.0.55 Platform: PC OS/Version: FreeBSD Status: NEW Keywords: PatchAvailable Severity: minor Priority: P2 Component: mod_proxy AssignedTo: [email protected] ReportedBy: [EMAIL PROTECTED] In a reverse proxy setup I encountered a problem with user directories; it seemed like every now and then users got redirected to http://host/%7Euser instead of the correct http://host/~user. After some debugging I figured out that the frontend mod_proxy was "canonicalizing" URLs, thereby encoding ~ as %7E. This would not be an issue but for lots of backend server software that relied on the URL passed to the backend server to be the same as the one the user saw in their browsers. Now, this is of course a bad assumption *but* I don't really know why the canonicalization happens in the first place, or even why ~ is not considered a safe character. I have attached a patch that simply adds '~' to the set of "reserved" characters for modules/proxy/proxy_util.c:ap_proxy_canonenc. It does the job on my site. Is there any reason not to apply it? Note: I tried to subscribe to apache-users@ to ask around for other people experiencing this bug bug the list never confirmed my emails... -- 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]
