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.
Are there any known problems with putting the HTTP Connection: field at the end of the headers?
From the Standard (RFC2616, section 4.2):
it is “good practice” to send general-header fields first (which includes
Connection), followed by request-header or response-header fields, and ending with the entity-header fields.
Am I gonna get bit if I violate the “good practice” for the Connection HTTP Header?
It is “good practice” only, not a requirement. HTTP implementations are required to support headers appearing in any order.