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.
HTTP specification (RFC2616) has the following phrase:
If a Transfer-Encoding header field (section 14.41) is present and
has any value other than “identity”, then the transfer-length is
defined by use of the “chunked” transfer-coding (section 3.6),
unless the message is terminated by closing the connection.
How can I detect that the message is “terminated by closing the connection”? Is it enough to check the “Connection” field for value “close”?
I think that the RFC points to the TCP connection, when you read 0 bytes from the socket, the other side has closed the connection.
More:
Can read() function on a connected socket return zero bytes?