24275 2014-01-13 06:12:27 +0000 Application cache vs HTTP Expires 2015-06-17 05:41:30 +0000 1 1 1 Unclassified HTML WG HTML5 spec unspecified PC Windows NT RESOLVED WONTFIX P2 editorial --- 1 vic99999 dave.null mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 98312 0 vic99999 2014-01-13 06:12:27 +0000 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! 121178 1 mike 2015-06-17 05:41:30 +0000 I think this is mostly "overcome by events" in that appcache is deprecated in practice (with Service Worker as the replacement) so what we probably need to do instead is add more disclaimers to the spec to indicate that author-developers should not use appcache (or maybe just go all the way and make the spec say that appcache is obsolete).