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

The client end of the handshake may receive payload data after "server finished" message #52

Open
mscottmueller opened this issue Jun 1, 2022 · 1 comment

Comments

@mscottmueller
Copy link

Because of receive segment coalescing and other TCP/IP behaviors (e.g. Nagle's algorithm), it is possible for some data payload to be present in the extra data buffers on the client end after the handshake is completed. We need a mechanism to detect and transfer this over to the input buffers for the subsequent receive cycle.

@laudrup
Copy link
Owner

laudrup commented Jun 1, 2022

This indeed sounds familiar and like something I've tried to handle but I must admit I can't remember the details.

Is this something you would be willing to look into or should I do that? In the latter case I would very much appreciate if you could explain this a bit more in details.

Thanks.

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