Current time: 03-06-2021, 09:52 AM Hello There, Guest! (LoginRegister)

Post Reply 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Caching Static Assets Issue
04-05-2013, 05:58 AM
Post: #1
Caching Static Assets Issue
WPT is complaining of errors in my caching, it's complaining that my assets do not have an expires or max-age tag, when in fact they do:

Test Results:

When I look at a specific asset:

$ curl -I
HTTP/1.0 200 OK
Content-Type: text/css
Content-Length: 28056
Connection: keep-alive
Date: Mon, 11 Mar 2013 20:04:03 GMT
Server: Apache/2.2.22
Last-Modified: Mon, 11 Mar 2013 19:05:28 GMT
ETag: "6d98-4d7aadb34afee"
Accept-Ranges: bytes
Cache-Control: max-age=31536000, public, must-revalidate, proxy-revalidate
Expires: Tue, 11 Mar 2014 20:04:03 GMT
Pragma: public
X-Powered-By: W3 Total Cache/
Age: 2072534
Vary: Accept-Encoding
Via: 1.0 (CloudFront)
X-Cache: Hit from cloudfront
X-Amz-Cf-Id: _yX6JvbSVqmktz6JlWD3IFfgv5fFmL6XfPzsELImnh0m1ZW2UjZyNQ==

$ curl -I
HTTP/1.1 200 OK
Accept-Ranges: bytes
Cache-Control: max-age=31536000
Cache-Control: max-age=31536000, public
Content-length: 28110
Content-Type: text/css
Date: Thu, 04 Apr 2013 19:52:35 GMT
Expires: Fri, 04 Apr 2014 19:52:35 GMT
Last-Modified: Fri, 29 Mar 2013 01:33:16 GMT
Pragma: public
Server: nginx
Vary: Accept-Encoding
Connection: keep-alive

Any help would be appreciated in resolving this.
Find all posts by this user
Quote this message in a reply
04-09-2013, 01:31 AM
Post: #2
RE: Caching Static Assets Issue
I'm not sure if it's explicitly what I detected but must-revalidate effectively disables the browser cache and forces the browser to always check with the server to make sure the version it has is current.
Visit this user's website Find all posts by this user
Quote this message in a reply
Post Reply 

Forum Jump:

User(s) browsing this thread: 1 Guest(s)