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=37347>. 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=37347 Summary: mod_disk_cache replaces HTTP Status 301 with 200 Product: Apache httpd-2.0 Version: 2.0.54 Platform: PC OS/Version: Linux Status: NEW Severity: major Priority: P2 Component: mod_disk_cache AssignedTo: [email protected] ReportedBy: [EMAIL PROTECTED] this is the same as 23550 except it applies to mod_disk_cache and does not occur in mod_mem_cache (so excuse the copying of the well stated report) When apache is configured as a reverse proxy with mod_disk_cache enabled (or both mod_disk_cache and mod_mem_cache but not with mod_mem_cache alone), it will cache 301 responses from the backend. Now, when we hit the memory-cached object, mod_disk_cache returns the original 301 response with a replaced HTTP status of 200. This causes clients to not follow the redirect. I will try to illustrate this: request: GET /foo HTTP/1.1 Host: www.foo.tld 1st response, before caching: HTTP/1.1 301 Moved Permanently Location: http://www.foo.tld/foo/ subsequent response, on same request: HTTP/1.1 200 OK Location: http://www.foo.tld/foo/ => Client ignores Location: header -- 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]
