- From: Drew Wilson <atwilson@google.com>
- Date: Wed, 22 Jul 2009 09:10:52 -0700
Not sure what you are suggesting, Anne - it sounds like they want to tie the AppCache to a specific cookie/value combination, which I don't believe is supported by the current spec. -atw On Wed, Jul 22, 2009 at 3:32 AM, Anne van Kesteren <annevk at opera.com> wrote: > On Wed, 15 Jul 2009 00:30:05 +0200, Aaron Whyte <awhyte at google.com> wrote: > > Most apps provide different contents for the same uncacheable main-page > > URL, depending on the identity of the user, which is typically stored in > a > > cookie and read by the server. > > However, the HTML5 AppCache spec doesn't allow cookies to influence the > > choice of AppCaches or the contents of a response returned by the cache. > > Why not? I cannot find anything like that in the specification. It seems to > me that the generic fetching algorithm is used which does not forbid sending > cookies and even explicitly calls out setting them. > > > -- > Anne van Kesteren > http://annevankesteren.nl/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20090722/fc238112/attachment.htm>
Received on Wednesday, 22 July 2009 09:10:52 UTC