On Thu, 11 Nov 2004, [EMAIL PROTECTED] wrote:
100156777.820 48 127.0.0.1 TCP_MISS/200 39 CONNECT 62.22.179.104:29829 - DIRECT/62.225.179.104 - [User-Agent: Mozilla/4.0\r\n] [] 1100156778.092 21 127.0.0.1 TCP_MISS/200 39 CONNECT 62.22.179.104:23248 - DIRECT/62.225.179.104 - [User-Agent: Mozilla/4.0\r\n] [] 1100156778.288 17 127.0.0.1 TCP_MISS/200 435 CONNECT 62.22.179.104:54794 - DIRECT/62.225.179.104 - [User-Agent: Mozilla/4.0\r\n] [] 1100156796.283 59 127.0.0.1 TCP_MISS/200 39 CONNECT 62.22.179.104:20186 - DIRECT/62.225.179.104 - [User-Agent: Mozilla/4.0\r\n] [] 1100156796.592 18 127.0.0.1 TCP_MISS/200 39 CONNECT 62.22.179.104:55367 - DIRECT/62.225.179.104 - [User-Agent: Mozilla/4.0\r\n] [] 1100156796.934 13 127.0.0.1 TCP_MISS/200 39 CONNECT 62.22.179.104:27064 - DIRECT/62.225.179.104 - [User-Agent: Mozilla/4.0\r\n] []
WTF is this? Are you intentionally abusing your HTTP proxy with a client intentionally lying about it's identity?
I think you should look into installing a SOCKS or FTP proxy in addition to Squid.
2004/11/11 09:28:53| authenticateDecodeAuth: Unsupported or unconfigured proxy-auth scheme, 'mckv?ud`|bn'
This part (mckv?ud`|bn) changes randomly.
Broken client sending invalid Proxy-Authorize: headers to Squid. You should be able to see these with log_mime_hdrs enabled.
Regards Henrik
