Is a website blocked in Chrome?

Question

According to the WebSocket Draft-76 specification, Wocket.close should do the following:

"To close the connection cleanly, a frame consisting of only 0xFF byte followed by 0 × 00 bytes is sent from one peer to ask another partner to close the connection."

But after several tests, I don’t think Chrome does anything when closed is called. I am curious if I am doing something wrong or if this is a known mistake.

Answer 1

I did not notice any problems when testing with Chrome. I also did not check frames.

Answer 2

I know this topic is really old, but I noticed that Chrome is the only browser that does not send 0xff00 to the close close command ... instead it closes its socket on the browser side, so if I notice that "chrome" The user is disconnected if I do not receive data from this socket. Only my two cents :)