Re: [squid-users] replacement for obsoleted cache controls (ign-no-cache; ign-must-reval. + ign-auth)

2020-12-09 Thread Amos Jeffries
On 9/12/20 11:14 am, L A Walsh wrote: On 2020/12/06 12:14, Alex Rousskov wrote: On 12/6/20 10:12 AM, L A Walsh wrote: Since the early 4.x series and now, the cache control headers: FTR: Since Squid-3.2 ignore-no-cache ignore-must-revalidate ignore-auth ... Thanks for the followup. 

Re: [squid-users] replacement for obsoleted cache controls (ign-no-cache; ign-must-reval. + ign-auth)

2020-12-08 Thread L A Walsh
On 2020/12/06 12:14, Alex Rousskov wrote: On 12/6/20 10:12 AM, L A Walsh wrote: Since the early 4.x series and now, the cache control headers: ignore-no-cache ignore-must-revalidate ignore-auth ... Thanks for the followup. One of the main things I try to use my proxy for is to

Re: [squid-users] replacement for obsoleted cache controls (ign-no-cache; ign-must-reval. + ign-auth)

2020-12-06 Thread Amos Jeffries
On 7/12/20 9:14 am, Alex Rousskov wrote: On 12/6/20 10:12 AM, L A Walsh wrote: ... * ignore-no-cache Squid v3.2 release notes imply that Squid does what most admins want now, without any explicit option: "Its commonly desired behaviour is obsoleted by correct HTTP/1.1 Cache-Control:no-cache

Re: [squid-users] replacement for obsoleted cache controls (ign-no-cache; ign-must-reval. + ign-auth)

2020-12-06 Thread Alex Rousskov
On 12/6/20 10:12 AM, L A Walsh wrote: > Since the early 4.x series and now, the cache control headers: > ignore-no-cache > ignore-must-revalidate > ignore-auth > have been "obsoleted".  Indicating something has replaced them and > there's a new & better way to ignore those headers for > static