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=15571>. 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=15571 No WWW-Authenticate header returned in 401 message ------- Additional Comments From [EMAIL PROTECTED] 2003-11-11 21:35 ------- I suspect that the fix below is what is needed. I haven't found the mod_dav 1.0 change yet, but I found this change entry: "if a lock fails due to authentication problems, return a 403 (Forbidden) rather than 401 (Unauthorized). this fixes an HTTP conformance issue where we returned 401 but no WWW-Authenticate response header. (Joe Orton)" I'm guessing this is Joe's fix... patch to 2.0's mod_dav: Index: util.c =================================================================== RCS file: /home/cvs/httpd-2.0/modules/dav/main/util.c,v retrieving revision 1.48 diff -u -r1.48 util.c --- util.c 22 Apr 2003 21:52:46 -0000 1.48 +++ util.c 11 Nov 2003 21:30:58 -0000 @@ -1212,7 +1212,7 @@ "\" submitted a locktoken created " "by user \"", lock->auth_user, "\".", NULL); - return dav_new_error(p, HTTP_UNAUTHORIZED, 0, errmsg); + return dav_new_error(p, HTTP_FORBIDDEN, 0, errmsg); } /* --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
