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 25070 - Is not clear what happens if the resource had an Expires or a max-age. Should it be fetched again or not?
Summary: Is not clear what happens if the resource had an Expires or a max-age. Should...
Status: RESOLVED WORKSFORME
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-03-15 14:39 UTC by contributor
Modified: 2014-03-18 18:37 UTC (History)
2 users (show)

See Also:

Attachments

Description contributor 2014-03-15 14:39:34 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/offline.html
Multipage: http://www.whatwg.org/C#downloading-or-updating-an-application-cache
Complete: http://www.whatwg.org/c#downloading-or-updating-an-application-cache
Referrer: https://www.google.es/

Comment:
Is not clear what happens if the resource had an Expires or a max-age. Should
it be fetched again or not?

Posted from: 88.13.98.211
User agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/33.0.1750.117 Safari/537.36
Comment 1 Ian 'Hixie' Hickson 2014-03-17 19:48:27 UTC 
The spec says "honor HTTP caching semantics (such as expiration, ETags, and so forth) with respect to that cache". Exactly what that means is defined in the HTTP spec, and is out of scope for HTML.
Comment 2 Ian 'Hixie' Hickson 2014-03-18 18:37:59 UTC 
Please reopen if that's not enough. Thanks.