W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > September 2009

[Bug 7689] Cache-defeating semantics are not defined

From: <bugzilla@wiggum.w3.org>
Date: Wed, 30 Sep 2009 07:27:41 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1MstbB-00034y-KA@wiggum.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=7689


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

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|                            |NEEDSINFO




--- Comment #5 from Ian 'Hixie' Hickson <ian@hixie.ch>  2009-09-30 07:27:40 ---
> From step 7.2 of Section 6.9.4, a non-normative note says
> [[
> HTTP caching rules, such as Cache-Control: no-store, are ignored for the
> purposes of the application cache update process.
> ]]
> 
> This contradiction suggests to me that all cache-related semantics need to be
> specified to the same level of rigor. 

This isn't a contradiction; it's a description of what the algorithm already
does. That is, the algorithm caches data from the server regardless of the
Cache-Control headers _from_ the server.

The bit you quoted at the very top of this bug is about user agents sending
cache-related headers _to_ the server, which is completely unrelated.


> My proposal is to either be specific in a normative manner about the kinds of
> cache semantics that must be ignored or may be permitted. The specific
> semantics that are actually applied are then bounded in this range.

Do you have any suggestions for what should _not_ be permitted? I don't really
understand what this would look like.


-- 
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 Wednesday, 30 September 2009 07:27:43 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:01 UTC