DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11751>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11751 200 status code logged when password file unreadable [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Major |Minor Priority|High |Low Summary|Logging 200 on hits that |200 status code logged when |shouldn't |password file unreadable ------- Additional Comments From [EMAIL PROTECTED] 2002-08-16 14:21 ------- You may have uncovered a small bug, but the configuration you are using is completely wrong. Where is apache supposed to get usernames/passwords if you set AuthUserFile to /dev/null? And you also shouldn't be using the <Limit> and </Limit> lines. Still, I would think apache should be returning 500 or 403 in a situation where there is a "require valid-user" but the password file can't be read. But what response is actually going to the client? Can you replicate this yourself? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
