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 24276 - Application cache vs HTTP Expires
Summary: Application cache vs HTTP Expires
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P3 editorial
Target Milestone: ---
Assignee: This bug has no owner yet - up for the taking
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-01-13 06:12 UTC by vic99999
Modified: 2015-06-17 03:20 UTC (History)
3 users (show)

See Also:


Attachments

Description vic99999 2014-01-13 06:12:55 UTC
Hello

It seems, the "application-cache" spec does not clearly tell about the difference between HTTP caching and "application-cache":

What if i have html page with http max-age header set to 1 year or with expires header?
(i searched with google, on stackoverflow, i cannot find any clear answer, most of pages about "appcache" just says, that it was design for offline and it is a good thing...)

http://www.w3.org/TR/html5/browsers.html#introduction-4

Introduction tells nothing about HTTP Expires headers of "clock.html",
but if Expires was used, the user will not see much difference between appcache and expires before expiration date and while page is not updated on the server, seems.

So, i think, some info on this may help.

Thank you!
Comment 1 Michael[tm] Smith 2015-06-17 03:20:31 UTC
Doesn't affect UA behavior and no indications that it's generally important to make any change here. Feel free to re-open if somebody plans to actually take any action on this.