W3C home > Mailing lists > Public > public-mobileok-checker@w3.org > May 2007

ACTION: The order of HTTP Headers

From: Jo Rabin <jrabin@mtld.mobi>
Date: Wed, 23 May 2007 12:43:36 +0100
Message-ID: <C8FFD98530207F40BD8D2CAD608B50B4335DE6@mtldsvr01.DotMobi.local>
To: <public-mobileok-checker@w3.org>

According to Section 4.2 of RFC 2616 [1]

   The order in which header fields with differing field names are
   received is not significant. However, it is "good practice" to send
   general-header fields first, followed by request-header or response-
   header fields, and ending with the entity-header fields.

   Multiple message-header fields with the same field-name MAY be
   present in a message if and only if the entire field-value for that
   header field is defined as a comma-separated list [i.e., #(values)].
   It MUST be possible to combine the multiple header fields into one
   "field-name: field-value" pair, without changing the semantics of the
   message, by appending each subsequent field-value to the first, each
   separated by a comma. The order in which header fields with the same
   field-name are received is therefore significant to the
   interpretation of the combined field value, and thus a proxy MUST NOT
   change the order of these field values when a message is forwarded.

For moki, I would prefer to maintain the ordering as received. I'm not
sure that this makes it either easier or harder select values ...

e.g. //primaryDoc//HTTPResponse[last()]/header[@name="charlie"] does not
depend on the ordering ...

Jo

[1] http://tools.ietf.org/html/rfc2616#section-4.2
Received on Wednesday, 23 May 2007 11:43:48 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:13:03 GMT