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=42091>. 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=42091 Summary: mod_proxy and case insensitivity conflict Product: Apache httpd-1.3 Version: 1.3.34 Platform: PC OS/Version: Linux Status: NEW Severity: minor Priority: P2 Component: mod_proxy AssignedTo: [email protected] ReportedBy: [EMAIL PROTECTED] I had the following rules: Rewrite /fu http://Backend/fu ProxyPassReverse /fu http://Backend/fu The request that's made to the backend (captured with tcpdump) showed the request was made to http://backend/fu The backend returned a Location: http://backend/bar in the headers, which wasn't captured and corrected to the frontend's site, but instead let it go to the browser which naturally couldn't resolve the hostname. Since hostnames are case insensitive, even if by human "error" a case is defined, the efective configuration should consistently use the same case (all undercase, or respect user defined case). My workaround was, naturally, to use only lowercase. This is a minor bug, but it really was annoying before we found out what happened. -- 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]
