- From: <bugzilla@jessica.w3.org>
- Date: Fri, 07 Jan 2011 01:12:41 +0000
- To: public-html@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11688 Summary: Please add a note about loading appcache master entries that are listed in NETWORK section Product: HTML WG Version: unspecified Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: HTML5 spec (editor: Ian Hickson) AssignedTo: ian@hixie.ch ReportedBy: ap@webkit.org QAContact: public-html-bugzilla@w3.org CC: mike@w3.org, public-html-wg-issue-tracking@w3.org, public-html@w3.org There is a long section in HTML5 describing loading of ambiguous entries: ------------------- If a resource is listed in the explicit section or as a fallback entry in the fallback section, the resource will always be taken from the cache, regardless of any other matching entries in the fallback namespaces or online whitelist namespaces. When a fallback namespace and an online whitelist namespace overlap, the online whitelist namespace has priority. The online whitelist wildcard flag is applied last, only for URLs that match neither the online whitelist namespace nor the fallback namespace and that are not listed in the explicit section. ------------------- It would be helpful to mention master entries here, as well. I've seen people list https://www.their_site.com in NETWORK section, and expect all resources not listed as explicit ones to be loaded from the network, including the HTML document. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
Received on Friday, 7 January 2011 01:18:03 UTC