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

[Eliezer Croitoru]

I was just reading at stackexchange and I got this nasty error:
2016/12/05 17:47:05 kid1| Accepting HTTP Socket connections at local=[::]:13129 remote=[::] FD 24 flags=9
2016/12/05 17:47:05 kid1| Accepting SSL bumped HTTP Socket connections at local=[::]:3128 remote=[::] FD 25 flags=9
2016/12/05 17:47:05| pinger: Initialising ICMP pinger ...
2016/12/05 17:47:05| pinger: ICMP socket opened.
2016/12/05 17:47:05| pinger: ICMPv6 socket opened
2016/12/05 17:47:05 kid1| WARNING: Cannot retrieve 'qa.sockets.stackexchange.com:80'.
2016/12/05 17:47:05 kid1| assertion failed: ../../squid-4.0.16/src/FwdState.cc:268: "!EBIT_TEST(entry->flags, ENTRY_FWD_HDR_WAIT)"
2016/12/05 17:47:05| removing PID file: /var/run/squid.pid
2016/12/05 17:47:05| Pinger exiting.
2016/12/05 17:47:15| Pinger exiting.

Eliezer

----
Eliezer Croitoru
Linux System Administrator
Mobile: +972-5-28704261
Email: eliezer at ngtech.co.il


-----Original Message-----
From: squid-dev [mailto:squid-dev-bounces at lists.squid-cache.org] On Behalf Of Amos Jeffries
Sent: Wednesday, November 30, 2016 1:56 PM
To: squid-dev at lists.squid-cache.org
Subject: Re: [squid-dev] [PATCH] Update refresh_pattern description regarding 'max' option

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.

Amos

_______________________________________________
squid-dev mailing list
squid-dev at lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-dev