DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7985>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7985 Broken functionality in Apache::Status when proxied [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID ------- Additional Comments From [EMAIL PROTECTED] 2002-04-21 17:20 ------- ProxyPassReverse only changes URLs in the headers of the HTTP response, it does not try and parse the body of the response (too expensive, and impossible to do reliably). As a result, this looks like a config issue rather than a bug. The general rule with reverse proxying is to keep the URI on the backend the same as on the frontend. ie, configure your backend perl URL to be <Location /test1/perl-status>. This ensure that when a backend website uses an absolute URL, such as "/perl-status/blah", it does not "jump out" of your carefully chosen URL space. Ideally all backend reverse proxied websites should use relative links, however in the real world this usually doesn't happen, thus the problem :(
