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

[Alexey Melnikov <[e-mail]>]

Hi,

Len Holgate wrote:

>Could someone explain the rationale behind how changing the header field for
>origin from Sec-WebSocket-Origin to Origin in v11 of the draft doesn't
>require a protocol version change?
>
>Surely an implementation of draft 08 which advertises itself as
>Sec-WebSocket-Version: 8 can now fail to interoperate with an implementation
>of draft 11 or 12 which also avertises itself as Sec-WebSocket-Version: 8.
>
>At the very least, a draft 08 implementation will now incorrectly interpret
>browser clients (implementing 11 or later) as non browser clients and if
>there are any draft 08 implementations that use origin specific "access
>control"...
>
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.

>Likewise the Sec-WebSocket-Version change also breaks protocol compatibility
>in that a draft 08 client would expect the response from the server to
>include the WebSocket-Version header and a draft 11 server only has to send
>it if the handshake fails...
>
I don't think I've made any intentional change in this area, I think 
I've only clarified the text that was already in the document. Please 
describe the behaviour you would like to see.