On 22/11/17 23:33, Ralf Hildebrandt wrote:
I was updating from squid-5.0.0-20171103-re3bf07f to squid-5.0.0-20171117-rd816577 (and I was also testing squid-5.0.0-20171117-r4d27d0a) today and immediately found lots of "BUG 3279: HTTP reply without Date:" messages in my log (cache_dir had been cleared upon start, meaning I'm starting with a clean slate!): 2017/11/22 11:16:02| BUG 3279: HTTP reply without Date:
... >
is this a known bug with the recent snapshot?
Yes, it still happens when a server delivers responses without a Date header. Though IIRC it is mostly seen in the cases where an IMS/INM conditional response is returning without a Date header (a message state which is forbidden in HTTP). Taking a wild guess I suspect they are probably occuring when a client revalidating its client-side cached content from one of the broken servers. Or slightly less likely one of the early responses in cache_mem right after the restart has the problem.
The patch joseph referred to synthesizes a fake Date header some time far in the past. Thus forcing the content to become 'stale' in the cache. That can either led to further refresh conditionals which perpetuate the problem, or to purging the object from cache - thus causing extra long fetch times for all traffic to that server.
Current Squid should only be logging that message at a relatively high debug level (not important anymore) and synthesizing a Date header only when the 2xx status is delivered to the client - the object cannot be used for revalidation due to the missing header.
Amos _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
