Re: [hybi] On changing Sec-WebSocket-Origin to Origin

Yes.  The protocol version needs to be incremented when there is a
non-backward-compatible handshake change as well as when there is a
non-backward-compatible change to the framing.  If we're changing the name
of the origin header, we absolutely need to also increment the version
number.

Brian

On Tue, Aug 30, 2011 at 9:12 AM, Len Holgate <len.holgate@gmail.com> wrote:

> A new server, yes, anything existing that thinks it implements protocol
> version 8 now doesn't implement draft HyBi-11's version of protocol version
> 8...
>
> > -----Original Message-----
> > From: John Tamplin [mailto:jat@google.com]
> > Sent: 30 August 2011 16:51
> > To: Len Holgate
> > Cc: Alexey Melnikov; Hybi
> > Subject: Re: [hybi] On changing Sec-WebSocket-Origin to Origin
> >
> > On Tue, Aug 30, 2011 at 6:00 AM, Len Holgate
> > <len.holgate@gmail.com> wrote:
> >
> >
> >       > Maybe not bumping the version number was a mistake.
> > The server can
> >       > handle either type of client, but this is not
> > explicitly mentioned in
> >       > the draft.
> >
> >
> >       How? If the server is only looking for
> > Sec-WebSocket-Origin (which a valid
> >       08 draft server could be) then it wont see the Origin
> > header from the v11
> >       client.
> >
> >
> > I server implementing v08 and v11 can look for both, the same
> > way existing servers support older versions of the protocol.
> >
> > --
> > John A. Tamplin
> > Software Engineer (GWT), Google
> >
> >
>
> _______________________________________________
> hybi mailing list
> hybi@ietf.org
> https://www.ietf.org/mailman/listinfo/hybi
>