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

Header longer then 512 bytes maybe incorrectly parsed #105

Open
brokkc1 opened this issue Oct 17, 2014 · 1 comment
Open

Header longer then 512 bytes maybe incorrectly parsed #105

brokkc1 opened this issue Oct 17, 2014 · 1 comment

Comments

@brokkc1
Copy link

brokkc1 commented Oct 17, 2014

As title suggests, during the handshake the connecting client sends a header that is longer then 512 bytes then it is possible for the connection to fail. It depends where the client places the security key (ie above the 512 cut off or below).

I fixed the issue by caching the header byte buffer and concatenating till the end of the HTTP header is received "\r\n\r\n" then parsing the cache at that point. Of cause increasing the buffer length may fix the issue, but that is until the a bigger payload arrives.

Happens with the latest Nuget release and latest build from GIT.

@mokeev1995
Copy link

Unforchantly, the last build at NuGet is really old. We should compile the last version from Git.

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

2 participants