I’ve a couple of questions regarding the Fastly caching:
- I’ve set the time for
stale-while-revalidateto 1 hour, however, the content served by Fastly was still stale after 1 hour when I checked.
- I’ve also set the
Expiresheader as below to
Sun, 19 Jul 2015 14:00:00 GMT, and the
Mon, 20 Jul 2015 00:42:08 GMT. However, Fastly is still serving the stale content and not respecting the
Could anyone please help? Thanks a lot in advance.
Request URL:http://www.***.com.au/***/movies Request Method:GET Status Code:200 OK Response Headers view source Accept-Ranges:bytes Age:4681 Cache-Control:max-age=3600, public, stale-while-revalidate=3600, stale-if-error=129600 Connection:keep-alive Content-Encoding:gzip Content-Length:12069 Content-Type:text/html; charset=utf-8 Date:Mon, 20 Jul 2015 00:42:08 GMT Etag:"a69fe485f49d6c3ecbc9096a74b80a05" Expires:Sun, 19 Jul 2015 14:00:00 GMT Server:Apache Status:200 OK Vary:Accept-Encoding Via:1.1 vegur Via:1.1 varnish Via:1.1 varnish X-Cache:MISS, HIT X-Cache-Hits:0, 2 X-Content-Type-Options:nosniff X-Frame-Options:SAMEORIGIN X-Request-Id:164f003d-0744-4780-b87b-04964f94e757 X-Runtime:0.397500 X-Served-By:cache-iad2125-IAD, cache-syd1625-SYD X-Timer:S1437352928.373283,VS0,VE0 X-Xss-Protection:1; mode=block
Please sign in to leave a comment.