if you open the hex cached file first header or so should be HTTP/1.1 200 OK right ??? is this correct in one line will be cacheable hit or corrupted accept-encodingHTTP/1.1 200 OK ??? good cache header file example HTTP/1.1 200 OK Via: cache-yes Content-Type: image/x-icon Last-Modified: Thu, 08 Jun 2017 16:42:39 GMT Content-Length: 1406 Server: Jetty(7.6.0.v20120127) --------------------------------------- bad cached header file accept-encodingHTTP/1.1 200 OK Accept-Ranges: bytes Content-Length: 158484 Last-Modified: Fri, 31 Mar 2017 23:01:45 GMT Server: ATS Vary: Accept-Encoding Connection: keep-alive Content-Type: video/mp2t Cache-Control: public, max-age=604800 Access-Control-Allow-Origin: * Access-Control-Expose-Headers: Content-Range, X-ATLAS-MARKERS Timing-Allow-Origin: * X-ATLAS-MARKERS: colodeb,cslrtt,rtt80_100ms,csbrtt,ar2,dist2000_3000km -- View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/cacheable-object-dose-not-match-tp4682776.html Sent from the Squid - Users mailing list archive at Nabble.com. _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
