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

Validation for First Three Messages being out of order is very weak #309

Open
RichardWarburton opened this issue Nov 27, 2019 · 0 comments

Comments

@RichardWarburton
Copy link
Contributor

RichardWarburton commented Nov 27, 2019

The SessionParser currently relies on a NumberFormatException with a specific message to hit a case where the first three fields are out of order. This should probably be dealt in a way that is less brittle to custom crafted out of order messages. Maybe even by the ReceiverEndPoint?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant