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.
When an application such as a web server sends HTTP data to a web browser, how does the browser know when it has received all of the data so that it can begin using it instead of waiting for more? TCP doesn’t specify anywhere how large a segmented message is going to be.
Right now I’m thinking that it’s up to the application layer, like HTTP’s Content-Length header. But it seems like even that header could be split off into a 2nd or 3rd packet.
Content-length indeed, except in the case where the client reads until it gets an end-of-file indication due to the other end closing the connection. Of course, in HTTP, ‘RSVP’, so that’s not going to happen.
Absent content length, it’s gotta look for
</html>or some other delimiter in the content. The browser doesn’t see packets at all. The connection looks like a stream, with no boundaries, and it’s up to the two ends to make a protocol.