- From: Simon Pieters <simonp@opera.com>
- Date: Fri, 07 May 2010 16:32:38 +0200
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'). -- Simon Pieters Opera Software
Received on Friday, 7 May 2010 07:32:38 UTC