The following reply was made to PR mod_proxy/2069; it has been noted by GNATS.
From: Marc Slemko <[EMAIL PROTECTED]> To: Erik Nedwidek <[EMAIL PROTECTED]> Cc: [EMAIL PROTECTED] Subject: Re: mod_proxy/2069: ProxyPass does not correctly handle link URL's Date: Thu, 16 Apr 1998 14:07:52 -0600 (MDT) On 16 Apr 1998, Erik Nedwidek wrote: > >Description: > I am proxying another server as > ProxyPass /mirror/dcertp http://w3.dcertp.raleigh.ibm.com You are saying that requests for the file /mirror/dcertp should be satisfied from http://w3.dcertp.raleigh.ibm.com. Apache has no reason to assume dcertp is a directory, because it could just as easily be a "file". If you want /mirror/dcertp/ (ie. a directory) to refer to http://w3.dcertp.raleigh.ibm.com, you need to use /mirror/dcertp/ instead. Note that this means that you need to add an explicit redirect from dcertp to dcertp/ if you want people to be able to access http://wolf/mirror/dcertp and not just http://wolf/mirror/dcertp/. > > When I click on a link to go to an html file that is hrefed as "news.html" > from > http://wolf/mirror/dcertp, I would expect to get the file > http://wolf/mirror/dcertp/news.html. Instead I get > http://wolf/mirror/news.html, > which fails. If I manually place the "dcertp" back into the URL, I get the > desired page. > >How-To-Repeat: > Servers are behind the firewall. Sorry :< > >Fix: > > >Audit-Trail: > >Unformatted: > [In order for any reply to be added to the PR database, ] > [you need to include <[EMAIL PROTECTED]> in the Cc line ] > [and leave the subject line UNCHANGED. This is not done] > [automatically because of the potential for mail loops. ] > > >
