Re: [squid-users] Default host_verify_strict behavior appears to have changed as of 3.5.25

2018-02-07 Thread steveno
OK this may be irrelevant to the "host_verify_strict" setting, its just when I looked at the messages like "2018/02/07 17:57:45 kid1| SECURITY ALERT: on URL: sqs.us-west-2.amazonaws.com:443" in the cache.log it led me to believe this was a feature of "RFC 2616 section 14.23" and that the default

Re: [squid-users] Default host_verify_strict behavior appears to have changed as of 3.5.25

2018-02-07 Thread Yuri
This irrelevant to host_verify_strict. This is effect of server side CDN IP changes. Squid threats it as security alert. 08.02.2018 00:03, steveno пишет: > I was using squid 3.5.20 I encountered an issue running out of File > Descriptors on Centos7, the scebario was that sockets would be

[squid-users] Default host_verify_strict behavior appears to have changed as of 3.5.25

2018-02-07 Thread steveno
I was using squid 3.5.20 I encountered an issue running out of File Descriptors on Centos7, the scebario was that sockets would be abandoned in a "CLOSE_WAIT" state forever until the server ran out of FD's. Searching I found the following BUG. https://bugs.squid-cache.org/show_bug.cgi?id=4508