Hi,
I am running squid-2.5STABLE4 with the patch regarding spaces in login names in an
actice directory environment. Squid gets usernames using NTLM and checks this using
external helper ip_user_check. This works fine, unfortunatly there are some usernames
with umlauts in them and those checks fail. When looking in access.log and cache.log I
see different username entries.
As an example we used a user with the name "n�":
access.log:
1064478528.646 14 192.168.1.11 TCP_DENIED/403 1716 GET
http://www.microsoft.com/isapi/redir.dll? domain\n%99 NONE/- text/html
cache.log:
2003/09/25 10:19:33| aclMatchExternal: groupcheck user not authenticated (-1)
2003/09/25 10:19:33| aclMatchExternal: groupcheck("192.168.1.11 domain\\n~Y") = lookup
needed
2003/09/25 10:19:33| externalAclLookup: lookup in 'groupcheck' for '192.168.1.11
domain\\n~Y'
2003/09/25 10:19:33| external_acl_cache_add: Adding '192.168.1.11 domain\\n~Y' = -1
2003/09/25 10:19:33| externalAclHandleReply: reply="ERR"
2003/09/25 10:19:33| external_acl_cache_add: Adding '192.168.1.11 domain\\n~Y' = 0
2003/09/25 10:19:33| aclMatchExternal: groupcheck = 0
The file ip_user_check uses contains a line
192.168.1.11 domain\\n�
and it is called with this line
external_acl_type groupcheck %SRC %LOGIN /usr/sbin/ip_user_check -f
/etc/squid/proxyuser.conf
So can squid handle usernames with umlauts at all and if so, how do those names get
encoded (or is this done by the browser?). Is there a difference between the encoding
regarding helpers and redirectors?
I would really appreciate any help or suggestion.
Jan
