Re: [squid-users] caching issues - caching traffic from another proxy, and caching https traffic
On 6/11/2015 4:47 a.m., John Smith wrote: > Amos, > > Thanks (again) very much for the reply. > The news does not surprise me at all, but I needed to ask the questions. > > Let's assume I could require a different port for http and https, and > cleaned up the squid configurations like we did privately for http. How > hard would it be to solve either caching problem at that point? Would that > solve problem #1 without taking any further action? Yes, at that point the caching would just work. Modulo any tuning you want to do. > At that point, how > hard would it be to implement ssl-bump? No more or less hard than it is for anyone else. Still a PITA, but possible. You would just need to be careful that the connections between the layers of proxies remains encrypted all the way through your system. Squid does not support sending secure content out over plain-text links. Amos ___ squid-users mailing list squid-users@lists.squid-cache.org http://lists.squid-cache.org/listinfo/squid-users
Re: [squid-users] caching issues - caching traffic from another proxy, and caching https traffic
Amos, Thanks (again) very much for the reply. The news does not surprise me at all, but I needed to ask the questions. Let's assume I could require a different port for http and https, and cleaned up the squid configurations like we did privately for http. How hard would it be to solve either caching problem at that point? Would that solve problem #1 without taking any further action? At that point, how hard would it be to implement ssl-bump? Thanks, John On Thu, Nov 5, 2015 at 7:31 AM, Amos Jeffries wrote: > On 5/11/2015 7:16 a.m., John Smith wrote: > > Hi, > > > > I'm trying to improve our cache hit ratio. We have a fairly complicated > > layer of squid 3.10 proxies as previously detailed. > > > > Problem 1. Some of the traffic is identified by domain to go to another > > layer of proxies. I've called this proxy otherl1proxy in the squid.conf > > below. I've noticed that this traffic is not cached at all on either set > > of proxies. I'd like it cached at the top layer if possible because > these > > will be the largest servers with the largest caches. I've removed > > 'originserver' from the squid.conf to test but that didn't seem to help. > > > > Problem 2. We are not caching any https traffic. Is it possible to > cache > > https traffic, and if so how would one do it? As many websites are > moving > > towards https for all traffic this lowers the effectiveness of cache... > > > > Hi John, > > Sorry to be the bearer of bad news. But problem #1 is another side > effect of the ELB situation. These will also come right back to the same > ELB problems, and the same multiple-ports solution. > > Every time you get that NAT failure message from the last issue we > discussed, the requests in that connection will not be cacheable. > > > As for #2, there is SSL-bump feature in Squid. But for your current > configuration it would be extremely painful to deal with. > > Amos > > ___ > squid-users mailing list > squid-users@lists.squid-cache.org > http://lists.squid-cache.org/listinfo/squid-users > ___ squid-users mailing list squid-users@lists.squid-cache.org http://lists.squid-cache.org/listinfo/squid-users
Re: [squid-users] caching issues - caching traffic from another proxy, and caching https traffic
On 5/11/2015 7:16 a.m., John Smith wrote: > Hi, > > I'm trying to improve our cache hit ratio. We have a fairly complicated > layer of squid 3.10 proxies as previously detailed. > > Problem 1. Some of the traffic is identified by domain to go to another > layer of proxies. I've called this proxy otherl1proxy in the squid.conf > below. I've noticed that this traffic is not cached at all on either set > of proxies. I'd like it cached at the top layer if possible because these > will be the largest servers with the largest caches. I've removed > 'originserver' from the squid.conf to test but that didn't seem to help. > > Problem 2. We are not caching any https traffic. Is it possible to cache > https traffic, and if so how would one do it? As many websites are moving > towards https for all traffic this lowers the effectiveness of cache... > Hi John, Sorry to be the bearer of bad news. But problem #1 is another side effect of the ELB situation. These will also come right back to the same ELB problems, and the same multiple-ports solution. Every time you get that NAT failure message from the last issue we discussed, the requests in that connection will not be cacheable. As for #2, there is SSL-bump feature in Squid. But for your current configuration it would be extremely painful to deal with. Amos ___ squid-users mailing list squid-users@lists.squid-cache.org http://lists.squid-cache.org/listinfo/squid-users
[squid-users] caching issues - caching traffic from another proxy, and caching https traffic
Hi, I'm trying to improve our cache hit ratio. We have a fairly complicated layer of squid 3.10 proxies as previously detailed. Problem 1. Some of the traffic is identified by domain to go to another layer of proxies. I've called this proxy otherl1proxy in the squid.conf below. I've noticed that this traffic is not cached at all on either set of proxies. I'd like it cached at the top layer if possible because these will be the largest servers with the largest caches. I've removed 'originserver' from the squid.conf to test but that didn't seem to help. Problem 2. We are not caching any https traffic. Is it possible to cache https traffic, and if so how would one do it? As many websites are moving towards https for all traffic this lowers the effectiveness of cache... squid.conf below Thanks, John # 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 transparent http_port 3130 # 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. 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 domain.com # Add any of your own refresh_pattern entries above these. refresh_pattern -i (robots\.txt)$ 60 40% 240 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 otherl1proxy parent 3128 0 no-query originserver no-digest name=other_l1_proxy acl sites_other_l1_proxy dstdomain .othersite.com cache_peer_access other_l1_proxy allow sites_other_l1_proxy cache_peer_access other_l1_proxy deny all cache_peer httpelb parent 80 0 no-query no-digest name=http_peer cache_peer_access http_peer allow httpacl cache_peer httpselb 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