Re: [hybi] "Establish a WebSocket Connection" does not allow for cookies

[Takeshi Yoshino <[e-mail]>]

On Wed, Sep 16, 2015 at 5:43 PM, Anne van Kesteren <[e-mail]> wrote:

> On Wed, Sep 16, 2015 at 10:20 AM, Takeshi Yoshino <[e-mail]>
> wrote:
> > It's not expecting any argument explicitly, but given the history of the
> > spec, I think we should just proceed to influence this by e.g.:
> >
> > Replace the second sentence of the step 9 of
> > https://html.spec.whatwg.org/multipage/comms.html#dom-websocket with
> >
> > When processing the step 12 of the requirements for an opening handshake
> > from a client described in the <a
> > href="https://tools.ietf.org/html/rfc6455#section-4.1">"Client
> Requirements"
> > section of  the WebSocket protocol specification</a>, include a Cookie
> > header whose value is the cookie-string computed from the user's cookie
> > store and the URL url; for these purposes this is not a "non-HTTP" API.
> > [WSP] [COOKIES]
>
> By "given the history of the spec" do you mean that we should not
> expect a clean fix to appear anytime soon on the IETF side and instead
> just use this monkey patch? I guess that's fine, it just seems far
>

I meant that we can see this as expecting an argument though it's not
explicitly expecting. In response to your comment "we cannot influence this
sentence".


> from ideal, especially given that it was done properly until draft
> eleven.
>
>
Ideally. Julian, do you think we can revive the identifier with a little
work? What's your thoughts after Anne's recent reply.


>
> --
> https://annevankesteren.nl/
>