This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 19354 - expires headers not applied to page assets
Summary: expires headers not applied to page assets
Status: RESOLVED WORKSFORME
Alias: None
Product: webplatform.org
Classification: Unclassified
Component: skin (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Doug Schepers
QA Contact: public-webplatform-bugs list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-10-08 17:19 UTC by Markus Glaser
Modified: 2012-10-25 06:12 UTC (History)
1 user (show)

See Also:

Attachments

Description Markus Glaser 2012-10-08 17:19:31 UTC 
It seems that docs sends an http header to disable broser caching
Comment 1 Paul Irish 2012-10-25 04:57:52 UTC 
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/
Comment 2 Paul Irish 2012-10-25 06:12:23 UTC 
webpagetest confirms files are cached. closing