- From: Anne van Kesteren <annevk@opera.com>
- Date: Fri, 06 Mar 2009 13:15:39 +0900
On Fri, 06 Mar 2009 12:56:43 +0900, Michael Nordman <michaeln at google.com> wrote: > On Thu, Mar 5, 2009 at 5:40 PM, Anne van Kesteren <annevk at opera.com> > wrote: >> Yes, cookies are no longer exposed through XMLHttpRequest in any way >> per the specification. > > So am i to understand that cookies headers are not sent to the servers > when using XHR, and that set-cookie headers in a server response to an > XHRs is not respected by the UA? Since that would break about every > known app in the world, I somehow think not. That's not what I said. > This is all you would need in order to set/read cookies from a worker > (albeit a very expensive operation), provided you had a server that > would cooperate with you. Fair enough, though Jonas (and I) were talking about setRequestHeader(), getAllResponseHeaders(), and getResponseHeader(). > Regarding being able to read/write cookies from a worker context... of > course you should be able to do that... if it takes an async api than > so be it. postMessage()? :-) -- Anne van Kesteren http://annevankesteren.nl/
Received on Thursday, 5 March 2009 20:15:39 UTC