You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is more of a question about the API. I was reviewing the API last night, and it seems a good place to intercept the growing incoming message size is:
WebSocketImpl
public void decode( ByteBuffer socketBuffer )
Please let me know if there's a better place to test for the incremental message size, or if this is already implemented somewhere. I'd like to prevent users, and or attackers from posting large amounts of data through the server by closing the connection once a certain size limit is reached.
thanks
-Mark
The text was updated successfully, but these errors were encountered:
This is more of a question about the API. I was reviewing the API last night, and it seems a good place to intercept the growing incoming message size is:
WebSocketImpl
public void decode( ByteBuffer socketBuffer )
Please let me know if there's a better place to test for the incremental message size, or if this is already implemented somewhere. I'd like to prevent users, and or attackers from posting large amounts of data through the server by closing the connection once a certain size limit is reached.
thanks
-Mark
The text was updated successfully, but these errors were encountered: