Bugzilla #114

The patch for 2.4 is simple, but HEAD has changed a lot and I don't
know if the patch is necessary there, or whats the best way to do it.
As a cop-out, I added some annoying debug message asking users to
report whether or not it works correctly.

diff --git a/src/acl.cc b/src/acl.cc
index 4122933509eb4bbc1f705885aace173aa84c4928..3798fa96cb1253851a64e3b670c4668c22b5bba1 100644 (file)
--- a/src/acl.cc
+++ b/src/acl.cc
@@ -1,6 +1,6 @@
 
 /*
- * $Id: acl.cc,v 1.254 2001/06/14 19:10:29 hno Exp $
+ * $Id: acl.cc,v 1.255 2001/06/28 20:16:30 wessels Exp $
  *
  * DEBUG: section 28    Access Control
  * AUTHOR: Duane Wessels
@@ -1326,6 +1326,11 @@ aclMatchProxyAuth(void *data, http_hdr_type headertype,
        return aclCacheMatchAcl(&auth_user_request->auth_user->
            proxy_match_cache, acltype, data,
            authenticateUserRequestUsername(auth_user_request));
+    } else {
+       debug(28, 1) ("XXX authenticateCheckAuthUserIP returned 0, somebody "
+           "make sure the username gets logged to access.log.\n");
+       debug(28, 1) ("XXX if it works, tell developers to remove this "
+           "message\n");
     }
     /* this acl check completed */
     authenticateAuthUserRequestUnlock(auth_user_request);