[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. ]
Synopsis: 404 errors disappear through mod_rewrite State-Changed-From-To: open-closed State-Changed-By: rse State-Changed-When: Tue Feb 24 07:27:11 PST 1998 State-Changed-Why: I've tested this now both under 1.2.5 and 1.3b6-dev and I both times get the correct answer in my access.log: 192.76.162.40 - - [24/Feb/1998:16:20:29 +0100] "GET /~rse/test HTTP/1.0" 404 162 Additionally I cannot see any reason why an URL manipulation by mod_rewrite should lead to a 200 response although the file does not exists. Because mod_rewrite does not handle this itself and the content handlers do not know anything about mod_rewrite's URL manipulations (or at least do not check for them). It has to to something with the particular additional modules (mod_jserv, mod_php) the user uses or with its local configuration. But I cannot find an error in mod_rewrite here.
