hi, I have a working(?) squid 3.10 proxy configuration. squid-3.1.10-29.18.amzn1.x86_64 on AWS Linux behind an AWS elastic load balancer.
My problem is that it appears every single AWS elastic load balancer healthcheck triggers a line like this in cache.log: 2015/10/28 22:35:10| IpIntercept.cc(137) NetfilterInterception: NF getsockopt(SO_ORIGINAL_DST) failed on FD 14: (92) Protocol not available I have determined that if I removed the 'intercept' option from our http_port 3128, we no longer get the warning messages in cache.log, but squid also no longer functions as we want it to... How do we resolve this?' Thanks! My squid.conf: # # Recommended minimum configuration: # acl manager proto cache_object acl localhost src 127.0.0.1/32 ::1 acl to_localhost dst 127.0.0.0/8 0.0.0.0/32 ::1 # Example rule allowing access from your local networks. # Adapt to list your (internal) IP networks from where browsing # should be allowed acl localnet src 10.0.0.0/8 # RFC1918 possible internal network acl localnet src 172.16.0.0/12 # RFC1918 possible internal network acl localnet src 192.168.0.0/16 # RFC1918 possible internal network acl localnet src fc00::/7 # RFC 4193 local private network range acl localnet src fe80::/10 # RFC 4291 link-local (directly plugged) machines acl httpacl port 80 acl SSL_ports port 443 acl Safe_ports port 80 # http acl Safe_ports port 21 # ftp acl Safe_ports port 443 # https acl Safe_ports port 70 # gopher acl Safe_ports port 210 # wais acl Safe_ports port 1025-65535 # unregistered ports acl Safe_ports port 280 # http-mgmt acl Safe_ports port 488 # gss-http acl Safe_ports port 591 # filemaker acl Safe_ports port 777 # multiling http acl CONNECT method CONNECT # # Recommended minimum Access Permission configuration: # # Only allow cachemgr access from localhost http_access allow manager localhost http_access deny manager # Deny requests to certain unsafe ports http_access deny !Safe_ports # Deny CONNECT to other than secure SSL ports http_access deny CONNECT !SSL_ports # We strongly recommend the following be uncommented to protect innocent # web applications running on the proxy server who think the only # one who can access services on "localhost" is a local user #http_access deny to_localhost # # INSERT YOUR OWN RULE(S) HERE TO ALLOW ACCESS FROM YOUR CLIENTS # negative_ttl 3600 seconds # Example rule allowing access from your local networks. # Adapt localnet in the ACL section to list your (internal) IP networks # from where browsing should be allowed http_access allow localnet http_access allow localhost # And finally deny all other access to this proxy http_access deny all # Squid normally listens to port 3128 http_port 3128 intercept # We recommend you to use at least the following line. hierarchy_stoplist cgi-bin ? # Uncomment and adjust the following to add a disk cache directory. cache_dir ufs /squid1 30720 16 256 cache_dir ufs /squid2 30720 16 256 cache_mem 10 GB access_log /logs/squid/access.log cache_log /logs/squid/cache.log # Leave coredumps in the first cache dir coredump_dir /var/spool/squid visible_hostname l1 # Add any of your own refresh_pattern entries above these. refresh_pattern -i \.(html|htm|css|js)$ 1440 40% 259200 refresh_pattern -i \.(gif|png|jpg|jpeg|ico|otf|woff|eot|ttf|svg)$ 10080 90% 259200 override-expire ignore-no-cache ignore-no-store ignore-private refresh_pattern ^ftp: 1440 20% 10080 refresh_pattern ^gopher: 1440 0% 1440 refresh_pattern -i (/cgi-bin/|\?) 0 0% 0 refresh_pattern . 0 20% 4320 cache_peer l2proxy parent 80 0 no-query no-digest name=http_peer cache_peer_access http_peer allow httpacl cache_peer l2proxy parent 3129 0 no-query no-digest name=https_peer cache_peer_access https_peer deny httpacl never_direct allow all
_______________________________________________ squid-users mailing list squid-users@lists.squid-cache.org http://lists.squid-cache.org/listinfo/squid-users
