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
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: