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.

Sign up for GitHub

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

Jump to bottom

Define a maximum message size and avoid useless parsing #37

Open
emiago opened this issue Aug 22, 2023 · 2 comments
Open

Define a maximum message size and avoid useless parsing #37

emiago opened this issue Aug 22, 2023 · 2 comments
Assignees
@emiago

Comments

@emiago
Copy link
Owner

emiago commented Aug 22, 2023

TCP/UDP could be larger message size which may lead lot of bad parsing and therefore processing

Original comment suggestion
#36 (comment)
@emiago emiago mentioned this issue Aug 22, 2023
Closed
@emiago
Copy link
Owner Author

emiago commented Sep 7, 2023

TCP/WS now has default stream parsing.

@emiago emiago self-assigned this Sep 7, 2023
@emiago
Copy link
Owner Author

emiago commented Oct 22, 2023

problem is multiple small messages that can still be in single flight.
This still is good for security to define.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@emiago emiago

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@emiago