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=20183>. 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=20183 ErrorDocument screws up proxied responses other than 200 OK [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | ------- Additional Comments From [EMAIL PROTECTED] 2004-04-15 19:18 ------- I'm reopening this because I'm running into a similar related issue. I'm using rewrite rules and proxying along with an ErrorDocument to do a load balancing configuration with failover when the proxy request fails. If the proxy can't hit the server and returns a 502, I use an ErrorDocument to force a redirect to the same URL after changing a cookie that tells it to try another server out of a rewrite map. The problem is that the 302 redirect is being treated as an error and subsequent requests never reach my ErrorDocument handler. When I read this report it sounds as if the patch was to treat anything other than 2xx as an error. Is a redirect truly an error? If so, then the only way I can achieve what I'm attempting is to send a 200 response with a META-REFRESH tag. I believe the code in http_request.c in ap_die() has the same issue where it checks if r->status != HTTP_OK. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
