[squid-users] "store-stale" sending original "expires" header may be breaking windows update?
squid3 at treenet.co.nz
Tue Dec 6 15:30:18 UTC 2016
On 7/12/2016 4:08 a.m., Heiler Bemerguy wrote:
> Hi folks, what do you think about it?
> refresh_pattern -i
> 483840 100% 483840 override-expire ignore-reload ignore-no-store
> A request sent to squid:
> Accept: */*
> User-Agent: Windows-Update-Agent
> Proxy-Connection: Keep-Alive
> Host: download.windowsupdate.com
> squid reply to the user:
> HTTP/1.1 200 OK
> *Expires: Thu, 17 Nov 2016 18:00:01 GMT*
> MSRegion: Latam
> Cache-Control: public,max-age=172800
> Content-Length: 0
> Content-Type: application/vnd.ms-cab-compressed
> Last-Modified: Mon, 14 Nov 2016 16:57:44 GMT
> Accept-Ranges: bytes
> ETag: "0b4d737983ed21:0"
> Server: Microsoft-IIS/8.5
> X-Powered-By: ASP.NET
> X-CID: 7
> X-CCC: US
> X-MSEdge-Ref: Ref A: A41379B47DAB430595652F948ADA374C Ref B:
> A3C4FE3E5EFF7E01F424A3DC08B40AF5 Ref C: Tue Dec 6 06:44:10 2016 PST
> *Date: Tue, 06 Dec 2016 14:44:10 GMT*
> X-Cache: MISS from proxycache2
> Age: 60080
> X-Cache: HIT from proxy
> Via: 1.1 proxycache2 (squid), 1.1 proxy (squid)
> Connection: keep-alive
> So.. it's sending a stale object, but it's saying to the user that the
> object is expired... is it right? I think windows update is aborting
Worse than that.
-> Last-Modified + Age is not even close to the Date value.
-> The CC:max-age=172800 says it expires at 16 Nov 2016 16:57:44 GMT.
-> Content-Length says it is 0 bytes of data. Yet there are non-zero
amount of object being transferred in your log records.
Something is getting very screwed up in those headers.
What versions of Squid are those two proxies?
More information about the squid-users