[Bug 8515] Would be nice to clarify how this interacts with https. Many browsers do not cache https data to disk at all and it would be nice for https based applications to have some way to take advantage of disk based cache for non-sensitive data.

http://www.w3.org/Bugs/Public/show_bug.cgi?id=8515


Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED




--- Comment #1 from Ian 'Hixie' Hickson <ian@hixie.ch>  2010-01-10 11:44:54 ---
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: Accepted
Change Description: see diff given below
Rationale: I added a note to the intro about HTTPS.

I also realised that I had made it possible for manifests on one https: origin
to cache files marked no-store on other https: origins, which was unintended.
I've changed the spec to require that https: manifests only cache same-origin
URLs.


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Sunday, 10 January 2010 11:44:55 UTC