Thank you very much Amos. Your support and the Squid product works very good for us. It is handling all of our traffic very well and have not had any issues since the change.
-----Original Message----- From: squid-users [mailto:squid-users-boun...@lists.squid-cache.org] On Behalf Of Amos Jeffries Sent: Tuesday, August 09, 2016 6:12 PM To: squid-users@lists.squid-cache.org Subject: Re: [squid-users] squid refresh_pattern / cache question On 10/08/2016 10:43 a.m., Berkes, David wrote: > > I have a question about the caching mechanism and "refresh_pattern" > specifically. I had the following configured for my company. Lateley there > have been complaints that people are seeing old pages and not the recent > content...specifically when going to > www.bbc.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.bbc.com&d=CwIGaQ&c=y6v6TkqbF5T5q8gzoA5_qyxfBe6wpRCKPt3qOZXx4sE&r=cEqld2WF5YXp35LOdsMCPdSMKFHyVQBUWZMc0D_9qzI&m=XTlkALphJqTeTc9DfX4Rm5TaIO-jZtR0yZQ0tNYNHOE&s=5GPJPKVFqHYAv0pEZYSGQSDS8GijxSR7NaGDZIjtvdM&e= > >. > > Im not actually sure what is not allowing the bbc.com pages to not get > updated, but at this point, I just want to let squid do normal caching > without any refresh_pattern or "fancy" settings. > > My question is will I still get caching features/benefits of squid after I > remove the "refresh_pattern" entries? Yes you will get caching. Just on a slightly different set of objects than are being cached now. The HTTP protocol defines an algorithm for heuristic caching. Which is based on the headers sent by the server (or not) for each object. All that refresh_pattern does is provide default values for the headers if the server did not send one or other. The ignore/override options make Squid calculate that algorithm as if certain header values were not sent even if they were. I suggest you try the following changes first though: * remove the ignore-no-cache ignore-no-store ignore-private options. * add the refresh_pattern for correctly handling dynamic content. This should be placed as second to last pattern, just above the '.' one. refresh_pattern -i (/cgi-bin/|\?) 0 0% 0 That should make your Squid obey the HTTP protocol more accurately. If the problem remains after those changes, then you need to take a closer look at what exactly is going on with those problem URLs. Amos _______________________________________________ squid-users mailing list squid-users@lists.squid-cache.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.squid-2Dcache.org_listinfo_squid-2Dusers&d=CwIGaQ&c=y6v6TkqbF5T5q8gzoA5_qyxfBe6wpRCKPt3qOZXx4sE&r=cEqld2WF5YXp35LOdsMCPdSMKFHyVQBUWZMc0D_9qzI&m=XTlkALphJqTeTc9DfX4Rm5TaIO-jZtR0yZQ0tNYNHOE&s=dcU9dnoc_YN_qUGX_4NE01SGVn7A52SB_O3E2dm7BIA&e= ________________________________ Piper Jaffray & Co. Since 1895. Member SIPC and NYSE. Learn more at www.piperjaffray.com. Piper Jaffray corporate headquarters is located at 800 Nicollet Mall, Minneapolis, MN 55402. Piper Jaffray outgoing and incoming e-mail is electronically archived and recorded and is subject to review, monitoring and/or disclosure to someone other than the recipient. This e-mail may be considered an advertisement or solicitation for purposes of regulation of commercial electronic mail messages. If you do not wish to receive commercial e-mail communications from Piper Jaffray, go to: www.piperjaffray.com/do_not_email to review the details and submit your request to be added to the Piper Jaffray "Do Not E-mail Registry." For additional disclosure information see www.piperjaffray.com/disclosures _______________________________________________ squid-users mailing list squid-users@lists.squid-cache.org http://lists.squid-cache.org/listinfo/squid-users
