> On Feb 12, 2016, at 1:34 AM, Muhammad Faisal <[email protected]> wrote: > > Hello, > Experts please explain what does X-Cache HIT mean in the below response > header? Is this hit from my ATS server or origin CDN? Because for several > other objects i can see my ATS in the "Server:" header so does it means the > object is cached where server header has our ATS/version?
Unless you have enabled the xdebug.so plugin, and triggered it in the request, this is likely coming from the origin. Maybe a peering CDN? Akamai? — Leif > > > HTTP/1.1 200 OK > Accept-Ranges: bytes > Age: 137073 > Cache-Control: max-age=2592000 > Connection: keep-alive > Content-Length: 19077 > Content-Type: image/jpeg > Date: Wed, 10 Feb 2016 19:23:11 GMT > ETag: "56587050-4a85" > Expires: Thu, 25 Feb 2016 18:31:09 GMT > Last-Modified: Fri, 27 Nov 2015 15:01:36 GMT > Server: ATS/6.1.1 > X-Cache: HIT > > Other Objects without X-Cache: > HTTP/1.1 200 OK > Accept-Ranges: bytes > Age: 304 > Cache-Control: public, max-age=604800 > CF-Cache-Status: HIT > CF-RAY: 273740b33a4b28f6-DXB > Connection: keep-alive > Content-Length: 9096 > Content-Type: image/png > Date: Fri, 12 Feb 2016 09:26:34 GMT > ETag: "cef130dd4160d11:0" > Expires: Fri, 19 Feb 2016 09:26:34 GMT > Last-Modified: Fri, 05 Feb 2016 18:20:17 GMT > Server: ATS/6.1.1 > Vary: Accept-Encoding > > Thanks > F.
