Re: [squid-users] urlParse: Illegal character in hostname
Ah, I did set that, forgot to undo and never made the connection. Thank you. On 2/9/2011 at 4:58 PM, in message 4362f9aa484687ab1128437ff2264...@mail.treenet.co.nz, Amos Jeffries squ...@treenet.co.nz wrote: On Wed, 09 Feb 2011 08:03:12 -0500, Winfield Henry wrote: Hello, I have seen lots of references to the above in the mailing list. It is stated it is not a problem with squid, rather the clients proxy technique. I am fine with that, but wondering how this may be excluded from the log files? The hostname it refers to are some strange encoded characters. Thanks, W The message is displayed because you chose to enable check_hostnames feature. These are the security warnings that feature produces. Where possible please track down how and why these mangled invalid URLs are appearing and try to get it fixed. Amos
[squid-users] urlParse: Illegal character in hostname
Hello, I have seen lots of references to the above in the mailing list. It is stated it is not a problem with squid, rather the clients proxy technique. I am fine with that, but wondering how this may be excluded from the log files? The hostname it refers to are some strange encoded characters. Thanks, W
Re: [squid-users] urlParse: Illegal character in hostname
On Wed, 09 Feb 2011 08:03:12 -0500, Winfield Henry wrote: Hello, I have seen lots of references to the above in the mailing list. It is stated it is not a problem with squid, rather the clients proxy technique. I am fine with that, but wondering how this may be excluded from the log files? The hostname it refers to are some strange encoded characters. Thanks, W The message is displayed because you chose to enable check_hostnames feature. These are the security warnings that feature produces. Where possible please track down how and why these mangled invalid URLs are appearing and try to get it fixed. Amos
