Marco Berizzi wrote:
> Here is:
>
> 172.16.1.116 - - [13/Jun/2002:14:20:01 +0200] "GET http://www.cert.org/
> HTTP/1.0" 407 1358 TCP_DENIED:NONE
> 172.16.1.116 - - [13/Jun/2002:14:20:01 +0200] "GET http://www.cert.org/
> HTTP/1.0" 407 1358 TCP_DENIED:NONE
> 172.16.1.116 - aive\mberizzi [13/Jun/2002:14:20:01 +0200] "GET
> http://www.cert.org/ HTTP/1.0" 403 1012 TCP_DENIED:NONE
So the logging of the username did work, and we should remove that message
from cache.log.
> then I have clicked on the refresh button:
[... allowed]
Which shows that the functionality similar to that of
"authenticate_ip_ttl_is_strict off".
Checking in the source I see that there is a undocumented option to make
max_user_ip strict. Try specifying -s before the number of allowed IP
addresses.
acl concurrent_browsing max_user_ip -s 1
Without the -s flag, max_user_ip just tries to be annoying to the user.
I'll try to add the -s flag to the squid.conf documentation.
Regards
Henrik
Received on Thu Jun 13 2002 - 11:00:38 MDT
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 17:08:40 MST