[Bug 24275] New: Application cache vs HTTP Expires

https://www.w3.org/Bugs/Public/show_bug.cgi?id=24275

            Bug ID: 24275
           Summary: Application cache vs HTTP Expires
           Product: HTML WG
           Version: unspecified
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HTML5 spec
          Assignee: dave.null@w3.org
          Reporter: vic99999@yandex.ru
        QA Contact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-admin@w3.org,
                    public-html-wg-issue-tracking@w3.org

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!

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Monday, 13 January 2014 06:12:30 UTC