- From: <bugzilla@jessica.w3.org>
- Date: Thu, 25 Oct 2012 04:57:52 +0000
- To: public-webplatform-bugs@w3.org
- Message-ID: <bug-19354-5733-X31QtWkJGS@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=19354 Paul Irish <paul.irish@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |paul.irish@gmail.com Summary|Browser cache disabled |expires headers not applied | |to page assets --- Comment #1 from Paul Irish <paul.irish@gmail.com> --- Looking at headers I'm seeing HTTP/1.1 200 OK Server: Apache/2.2.14 (Ubuntu) X-Powered-By: PHP/5.3.2-1ubuntu4.18 X-Content-Type-Options: nosniff Content-language: en Cache-Control: s-maxage=18000, must-revalidate, max-age=0 Last-Modified: Wed, 17 Oct 2012 07:41:45 GMT Content-Encoding: gzip Content-Type: text/html; charset=UTF-8 Content-Length: 11986 Accept-Ranges: bytes Date: Thu, 25 Oct 2012 04:51:41 GMT Age: 460 Via: 1.1 varnish Connection: keep-alive X-Served-By: cache-s30-SJC2 X-Cache: HIT X-Cache-Hits: 1 X-Timer: S1351140701.822546721,VS0,VE0 Vary: Accept-Encoding,Cookie -- We have last modified, so subsequent refreshes trigger a 304. This works as expected. Nonpage resources like woff fonts are re-requested on all views. This is an opportunity for some medium-length expires headers. http://www.webpagetest.org/result/121025_QM_3WC/ -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Thursday, 25 October 2012 04:57:53 UTC