15700 2012-01-24 22:23:11 +0000 appcache: Prevent sensitive data from being cached 2013-04-24 16:20:13 +0000 1 1 1 Unclassified HTML WG HTML5 spec unspecified PC All RESOLVED WONTFIX CR P2 normal --- 1 tobie.langel robin ian mike plh public-html-admin public-html-wg-issue-tracking robin public-html-bugzilla oldest_to_newest 63081 0 tobie.langel 2012-01-24 22:23:11 +0000 Currently, the editor's draft allows preventing content from being cached by using the no-store http header. Often, developers cannot or do not know how to modify http headers to block sensitive parts of a website from being cached (when visited) by AppCache. e.g.: A website containing both public and sensitive HTML pages needs to be made available offline. The sensitive data must not be stored on the device. The website is hosted on a virtual host and HTTP headers cannot be modified. The web developer can prevent such pages from being cached by specifying them directly in the manifest. 63475 1 ian 2012-01-31 23:24:05 +0000 Why would any pages be cached if they're not listed in the manifest? Also, who on earth is dealing with sensitive data yet can't change caching headers? That's a frightening thought. 66116 2 tobie.langel 2012-03-27 14:16:09 +0000 (In reply to comment #1) > Why would any pages be cached if they're not listed in the manifest? They'd be cached as master entries simply by being visited. 70103 3 contributor 2012-07-18 06:54:23 +0000 This bug was cloned to create bug 17816 as part of operation convergence. 81697 4 robin 2013-01-21 15:58:49 +0000 Mass move to "HTML WG" 81815 5 robin 2013-01-21 16:01:35 +0000 Mass move to "HTML WG" 86685 6 robin 2013-04-24 16:20:13 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the Editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the Tracker Issue; or you may create a Tracker Issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Rejected Change Description: none Rationale: This will be addressed by NavCon.