[squid-dev] [PATCH] Update refresh_pattern description regarding 'max' option

Amos Jeffries squid3 at treenet.co.nz
Wed Nov 30 11:56:00 UTC 2016

On 21/11/2016 9:58 a.m., Garri Djavadyan wrote:
> The patch adds description for undocumented behavior related to 'max'
> option of 'refresh_pattern' directive. I mean, 'max' option sets value
> for 'Cache-Control: max-age' header sent by Squid upstream. Feel free to
> modify the description. Thanks.

IIRC it is not supposed to affect just any request. Only;
 a) the revalidation updates to HIT content need max-age, and that is to
ensure newer data comes back.
 b) sibling cache requests, because the content retrieved from a sibling
cache is supposed to be cacheable (thus within max storable age).

That (b) situation is one we probably should remove. But it needs
someone to analyse the use cases and figure out what should be going on
now in the HTTP/1.1 era.


More information about the squid-dev mailing list