[squid-users] Squid caching broken responses

[tomsl]

I have an odd issue running squid 4.2 as a reverse proxy in front of
rackspace cloudfiles. For some reason, something went wrong when the request
was made initially and squid has cached a broken response. The headers
returned by squid are as follows:

HTTP/1.1 200 OK
Accept-Ranges: bytes
Last-Modified: Tue, 20 Aug 2019 10:30:08 GMT
ETag: 9295f2e13cde446a4c6812163840f908
Content-Type: text/html; charset=UTF-8
Content-Length: 0
Date: Mon, 02 Dec 2019 10:41:17 GMT
Age: 167529
Warning: 113 squid/4.2 "This cache hit is still fresh and more than 1 day
old"
X-Cache: HIT from qa-stat-prox
X-Cache-Lookup: HIT from qa-stat-prox:80
Connection: keep-alive
Access-Control-Allow-Origin: *

----------------------------------------

When disabling the cache, the correct headers returned for this particular
file are:

HTTP/1.1 200 OK
Content-Length: 28272
Accept-Ranges: bytes
Last-Modified: Tue, 20 Aug 2019 10:30:08 GMT
ETag: 9295f2e13cde446a4c6812163840f908
Content-Type: image/jpeg
Date: Wed, 04 Dec 2019 09:20:44 GMT
X-Cache: MISS from qa-stat-prox
X-Cache-Lookup: MISS from qa-stat-prox:80
Connection: keep-alive
Access-Control-Allow-Origin: *

Is there a way I can stop it from caching the "broken" responses?




--
Sent from: http://squid-web-proxy-cache.1019090.n4.nabble.com/Squid-Users-f1019091.html