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

Question

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?

score 4 · Accepted Answer · answered Dec 28 '11 at 01:43

4

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

answered Dec 28 '11 at 01:43

Remy Lebeau

555,201
31
458
770

1

Then why is it good practice, if there exist no broken implementations? – unixman83 Dec 28 '11 at 01:46
3

Such "broken implementations" have not really existed anymore for a LONG time. Here is an interesting perspective on the issue: http://mark.stosberg.com/blog/2010/01/generating-http-headers-sorted-or-unsorted.html – Remy Lebeau Dec 28 '11 at 02:27

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

1 Answers1