W3C home > Mailing lists > Public > whatwg@whatwg.org > June 2010

[whatwg] WebSocket set-cookie

From: Simon Pieters <simonp@opera.com>
Date: Thu, 03 Jun 2010 15:46:14 +0200
Message-ID: <op.vdp8jc07idj3kv@simon-pieterss-macbook.local>
On Fri, 07 May 2010 16:32:38 +0200, Simon Pieters <simonp at opera.com> wrote:

> establish a WebSocket connection
>
> [[
> 41. ...
>
> If the entry's name is "set-cookie" or "set-cookie2" or another  
> cookie-related field name
> If the relevant specification is supported by the user agent, handle the  
> cookie as defined by the appropriate specification, with the resource  
> being the one with the host host, the port port, the path (and possibly  
> query parameters) resource name, and the scheme http if secure is false  
> and https if secure is true. [COOKIES]
>
> If the relevant specification is not supported by the user agent, then  
> the field must be ignored.
> ]]
>
> At this point, the handshake can still fail. It seems bad to set cookies  
> if the handshake fails. We want to process set-cookie when the handshake  
> has succeeded (but before changing readyState and firing 'open').

...but still in that same task that changes readyState and fires 'open'.

-- 
Simon Pieters
Opera Software
Received on Thursday, 3 June 2010 06:46:14 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:24 UTC