Catching message exceeding maxPayload without automatically closing the connection about ws HOT 4 CLOSED

I've tried adding on('error') listeners, and I can successfully "catch" the Error on the server side, but it seems like the library automatically closes the connection when this occurs? Is this the intended behaviour or am I likely not holding it correctly?

Yes, it is. The connection is closed with the 1009 status code when this happens. See https://www.rfc-editor.org/rfc/rfc6455.html#section-7.4.1.

from ws.

Ok, thanks for clarify that I'm at least not holding it incorrectly!

I'm not familiar with the rest of the specs, do they prescribe that a server must close the connection with 1009? Or just that if the server closes the connection due to exceeding the maximum payload size then it should use the 1009 code, and the only valid condition for returning 1009 code is due to exceeding the maximum payload size (i.e. don't use it for other reasons)

It seems unnecessary to have the server close the connection when it receives a message that is too large, when being able to handle it internally on the server as an "error" (in my case, sending back a message to the client to tell them it was too large) but continue to keep the connection open for more messages, but I'm not sure if that's just a fundamental misunderstanding of mine of the websocket protocol

from ws.

I think it is not mandatory but the behavior is common in the WebSocket implementations.

1. It is a measure against a possibile DoS attack.
2. If the connection is not closed, how do you handle these messages? Discarding them?
3. The size is configurable.
4. The endpoint is still informed of the problem via the close code.

from ws.

I'm closing this as answered.

from ws.