Is it expected behaviour for the main page to have no-cache control set?
-
I am trying to optimise my site and was looking at the waterfall chart (https://gtmetrix.com/reports/pewpewpew.cc/iIlEvZR5). I realised that the response headers for my main page is as follows:
Response Headers cache-control public, max-age=2592000 last-modified Fri, 22 Jun 2018 04:20:31 GMT status 200 date Fri, 22 Jun 2018 05:23:47 GMT vary Accept-Encoding content-encoding br cdn-cache HIT cdn-cachedat 2018-06-22 01:23:47 content-type application/javascript server BunnyCDN-WA1-368 link <https://pewpewpew.cc/min/24e31.js>; rel="canonical" alt-svc quic=":443"; ma=2592000; v="35,37,38,39" cdn-uid cfaa817a-7f3c-424f-91de-33c8f02b2533 cdn-pullzone 40420 cdn-requestid 046502737291d1535321cdd90023e858 expires Sun, 22 Jul 2018 04:40:12 GMT Request Headers user-agent Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537 .36 accept */* :method GET accept-language en-US,en;q=0.9 accept-encoding gzip, deflate, br :authority cdn.pewpewpew.cc :scheme https :path /min/24e31.js referer https://pewpewpew.cc/
I was wondering if this is the expected behaviour or if I’ve any settings done wrongly? Thanks!
The page I need help with: [log in to see the link]
Viewing 3 replies - 1 through 3 (of 3 total)
Viewing 3 replies - 1 through 3 (of 3 total)
- The topic ‘Is it expected behaviour for the main page to have no-cache control set?’ is closed to new replies.