The following reply was made to PR general/2724; it has been noted by GNATS.
From: Marc Slemko <[EMAIL PROTECTED]> To: Seth Chaiklin <[EMAIL PROTECTED]> Cc: [EMAIL PROTECTED] Subject: Re: general/2724: a permanent redirect (status code 301) to a non-existent file produces a status code 403 (HTTP_FORBIDDEN) instead of 404 (HTTP_NOT_FOUND) Date: Tue, 28 Jul 1998 23:22:33 -0700 (PDT) On 28 Jul 1998, Seth Chaiklin wrote: > Have a permanent redirect like this (in srm.conf): > > Redirect permanent /~bo http://www.psy.aau.dk > > Happened that one of the redirects was to a nonexistent file. > Here is an example from the access log file, which shows > that the redirect (301) gives a "forbiddden" error (403), when in reality > it should give a "not-found" (404). > > ocelot.eng.pgh.lycos.com - - [28/Jul/1998:00:52:05 +0200] "GET > /~bo/staff/stats. > html HTTP/1.0" 301 242 > ocelot.eng.pgh.lycos.com - - [28/Jul/1998:00:52:58 +0200] "GET > /staff/stats.html > HTTP/1.0" 403 214 Erm... what does this have to do with the redirect? Any access to /staff/stats.html gives the same error regardless of the redirect. Somehow, you have your server configured to deny access to the file. This can be configured even though the file doesn't exist.
