http-headershttpconnectiontransparentproxy

Real world problems with placing the HTTP Connection: Header at the end

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?

Solution

  • It is "good practice" only, not a requirement. HTTP implementations are required to support headers appearing in any order.