From: "Rodent of Unusual Size" <[EMAIL PROTECTED]> Sent: Thursday, January 31, 2002 11:39 AM
> Greg Ames wrote: > > > > /builds/tomcat/ is redirected to /builds/jakarta-tomcat/ via an > > .htaccess file, so the bottom two refer to the same thing. > > This actually exposes a new issue: invalid redirect fields. > > GET /builds/tomcat/ HTTP/1.0 > Host: jakarta.apache.org > > returns > > Location: /builds/jakarta-tomcat/index.html > > The 'index.html' is one problem, new since 2.0.28. And were the original issue not misbehaving, this 'problem' you cite is correct behavior. E.g. both get /builds/tomcat/ and /builds/tomcat/index.html would return Location: /builds/tomcat/index.html which is a very appropriate use for the Location field [what is the location we actually returned? index.html.] BUT that's not what I see right now; HEAD /builds/tomcat/ HTTP/1.0 Host: jakarta.apache.org HTTP/1.1 302 Found Date: Thu, 31 Jan 2002 18:33:37 GMT Server: Apache/2.0.28 (Unix) Location: /builds/jakarta-tomcat/ Connection: close Content-Type: text/html; charset=iso-8859-1 > However, the invalid absoluteURI issue is present even back in 2.0.28. > > The relevant line in the .htaccess file is: > > RedirectMatch /builds/tomcat/(.*) /builds/jakarta-tomcat/$1 > > Since there's no '[R]' flag, I'm not sure why this is forcing > an external redirect, either, rather than keeping it internal > and concealed from the client. Sounds like the external redirect is really /builds/jakarta-tomcat/ -> /builds/jakarta-tomcat/index.html Just a hunch.
