Re: os-linux/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)

[fi...@apache.org]

[In order for any reply to be added to the PR database, you need]
[to include <ap...@Apache.Org> in the Cc line and make sure the]
[subject line starts with the report component and number, with ]
[or without any 'Re:' prefixes (such as "general/1098:" or      ]
["Re: general/1098:").  If the subject doesn't match this       ]
[pattern, your message will be misfiled and ignored.  The       ]
["apbugs" address is not added to the Cc line of messages from  ]
[the database automatically because of the potential for mail   ]
[loops.  If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request from a  ]
[developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]


Synopsis: a permanent redirect (status code 301) to a non-existent file produces a  status code 403 (HTTP_FORBIDDEN)  instead of 404 (HTTP_NOT_FOUND)

State-Changed-From-To: open-closed
State-Changed-By: fielding
State-Changed-When: Sun Aug 15 01:42:10 PDT 1999
State-Changed-Why:

Apache defaults to forbidden if it doesn't recognize the
error response code, which in this case is a nonstandard
error message rather than what would be expected.  There
is no harm is this, since 403 is intended to be a general
response for inaccessible resources.

....Roy

Category-Changed-From-To: general-os-linux
Category-Changed-By: fielding
Category-Changed-When: Sun Aug 15 01:42:10 PDT 1999