Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I used WireShark to analyze the HTTP protocol, I found that a HTTP request which was large enough will be disassembled into several TCP packets like this: HTTP request method as a packet; HTTP request headers as a packet and HTTP content as a packet.
My question is: Is the TCP segments division decided by upper layer protocol or some other way?
For HTTP you might find this article interesting, how Google basically have their HTTP server interacting with TCP to push the initial segments without waiting for a response.
http://blog.benstrong.com/2010/11/google-and-microsoft-cheat-on-slow.html
And a RFC draft published here:
https://datatracker.ietf.org/doc/html/draft-hkchu-tcpm-initcwnd-01