Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DoS attacks #262

Closed
mwambler opened this issue May 16, 2014 · 1 comment
Closed

DoS attacks #262

mwambler opened this issue May 16, 2014 · 1 comment

Comments

@mwambler
Copy link

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

@marci4
Copy link
Collaborator

marci4 commented Sep 6, 2018

This issue is implemented with #598.

Best regards,
marci4

@marci4 marci4 closed this as completed Sep 6, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants