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/1.1 servers default to the Keep-Alive setting of the Connection header. Why
then do most browsers include Connection: Keep-Alive in their requests even when
they know that the target server supports HTTP/1.1?
Browsers usually don’t keep a cache of metadata about the servers they’ve contacted in the past, and even if they did, they’d have to account for server farms that have different versions of HTTP, intermediaries (especially “transparent” proxies), and so forth.
As such, they’ve made a judgement call that it’s just easier to always send Connection: keep-alive, at least on the first request in a connection.