Re: [squid-users] how debug google status codes in log file

On 19/06/18 17:12, --Ahmad-- wrote: > hello folks > how debug google status codes in log file ? > see the FAQ > in wiki i see we have : > > 1529368601.307 60038 184.154.133.146 TAG_NONE/503 0 CONNECT > www.google.com.et:443 fifox

Re: [squid-users] Use additional details in SAN field to build ACLs

On 06/18/2018 09:36 PM, Ahmad, Sarfaraz wrote: > Can I leverage other information available in a server certificates’s > SAN field to build my ACLs ? Unfortunately, Squid does not have ACLs that can match non-dNSName[1] parts of the Subject Alternative Name extension. [1] https://tools.ietf.org/

[squid-users] YUM Repo

Hi, there are problems with the yum repo? > http://www1.ngtech.co.il/repo/centos/6/x86_64/ When i try to sync with our local pulp server, come e timeout. thanks ___ squid-users mailing list squid-users@lists.squid-cache.org http://lists.squid-cache.o

Re: [squid-users] how debug google status codes in log file

Hi Ahmad, every HTTPS connection is TUNNELED through squid, as long as you do not intercept SSL traffic (SSLbump). You can only get either a 200 return code or error codes connected to failure of the connection, e.g. proxy authentication required, deny (by proxy) or network/dns issues. You will