Re: [hybi] RFC6455 clarification: when received close code of 1005, 1006, 1015

[Jason Duell <[e-mail]>]

On Mon, May 21, 2012 at 11:18 PM, Takashi Toyoshima
<[e-mail]> wrote:
> I'll fix WebKit implementation of receiving 1005, 1006, 1015, and
> length=1 of close frames.
> These frames will fire CloseEvent with code=1006 and wasClean=false.

What, if anything, do you plan to reply to the endpoint with, if the
1005/1006/1015 is received before your client has sent its own close
frame?  Will you be replying with 1002, but delivering 1006 to
onclose?  I can see the logic there, though it's a little confusing.
The only other choice would seem to be to simply shut down the TCP
connection with no close frame, but that seems harsh.  Or we could
both send 1002 to the remote server and deliver it to onclose (though
I agree that 1006 seems closer in meaning).

Jason Duell
Mozilla

>> We can. But as Arman suggested, we can also just use the existing code 1002
>> to tell the remote endpoint that it's broken when the closing handshake
>> initiator is the remote endpoint.