On 29/02/2016 4:57 p.m., Anonymous cross wrote: > I tried using "ignore-cc" option but still squid is honoring cache-control > header. It tries to re validate the cache on every HTTP request. The > configurations are below. > Please correct me if anything is wrong. > > *Squid.conf* > http_port 3128 > http_port 3129 tproxy > http_port 80 accel defaultsite=abcexample.com ignore-cc > cache_peer abcexample.com parent 80 0 no-query originserver name=myAccel > > acl our_sites dstdomain abcexample.com > http_access allow our_sites > cache_peer_access myAccel allow our_sites > cache_peer_access myAccel deny all > > *Option used* > curl -H "cache-control:no-cache" --interface "20.10.10.2" > http://abcexample.com -x localhost:3128 > You are not testing the reverse-proxy capabilities. You are testing the forward-proxy access. You *want* the forward proxy access (aka admin access) controls to be able to purge and update the cache entries like that. Remove the -X parameter from your curl command, and run the test from a separate machine like a real client would be. If you dont see any change, then you may need to add a bypass (divert chain rule setting the mark) to the TPROXY rules to prevent it capturing the port 80 traffic destined directly to the proxies port 80. It should only be capturing port 80 traffic destined to other servers. Amos _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
