Can anyone tell me any limitations that they have seen with this patch
installed?
IP based NTLM authentication cache
Goal: Efficient use of the proxy while using NTLM authentication
Status: Operational, but not supporing child proxies
CVS tag: ntlm_ip_cache
Based on: HEAD
Patch: view / download
Owner: Henrik Nordström
I would like to install this patch into production, but not sure if
there are any limitations or optimal settings for the TTL parameter.
Currently in production I am seeing during any 10 minute period that
there might be 800 concurrent users and during any 1 hour period there
might be 2000 concurrent users. I was planning to set the
authenticate_ip_shortcircuit_ttl 60 seconds. This seems to lower the
number of authentications by about 85% over no NTLM authentication
caching with the test group of about 60 users.
# grep 16.Jul.2009.13: access.log |wc -l
665182
# grep 16.Jul.2009.13: access.log |awk '{print $3}' |sort -u |wc -l
2000
# grep 16.Jul.2009.13:1 access.log |wc -l
122093
# grep 16.Jul.2009.13:1 access.log |awk '{print $3}' |sort -u |wc -l
775
Any information about using this patch would be greatly appreciated,
whether it is positive or negative.
Thank you,
Brian Kirk
