Chrome issue

Hi Jay,

this is most likely a caching issue, that is the web server isn’t sending the correct cache control headers.

Here’s a header dump:

duncan$ curl --head Road Tanker News - Abbey Logistics Group
HTTP/1.1 200 OK
Server: nginx/1.10.2
Date: Thu, 24 Nov 2016 10:34:33 GMT
Content-Type: text/html
Content-Length: 29068
Connection: keep-alive
Last-Modified: Wed, 23 Nov 2016 16:10:59 GMT
Accept-Ranges: bytes
Vary: Accept-Encoding

It should include an “Expires” such:

Expires: Thu, 24 Nov 2016 10:40:38 GMT

If your web host lets you configure server caching policy via a .htaccess file then putting a file named “.htaccess” with these contents in the root of your site might help:

# expire html immediately ExpiresActive On ExpiresByType text/html "access plus 0 seconds" # images, css and js for 7 days ExpiresDefault "access plus 7 days" Header set Cache-Control "public, max-age=604800"

(the server reports as nginx, which doesn’t directly support .htaccess, but the web host setup might be such that there’s an apache server on their backend and nginx is just a server-side caching frontend)

Otherwise you might try asking your web host how to have the server produce the correct caching headers.

Duncan
http://sparkle.cx http://sparkle.cx/ (<- on sale for black friday!)


freewaytalk mailing list
email@hidden
Update your subscriptions at: