W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2003

RE: Relative ordering of fields in HTTP request

From: Joris Dobbelsteen <joris.dobbelsteen@mail.com>
Date: Wed, 5 Nov 2003 17:04:19 +0100
To: "'Srikanth Kandula'" <kandula@MIT.EDU>, <ietf-http-wg@w3.org>
Message-Id: <20031105160333.6C0E213A20@dr-nick.w3.org>

There is no way to enforce an order of the headers.

The server has no say over the data it receives, except that it could deny
or accept the request. One should look at the entire request as a whole and
not scan through it expecting ordering.

Next a proxy is allowed to relocate headers or compact them if it wants to.
For example, multiple 'Accept' headers could be compacted into a single
'Accept' header.

- Joris

> -----Original Message-----
> From: ietf-http-wg-request@w3.org 
> [mailto:ietf-http-wg-request@w3.org] On Behalf Of Srikanth Kandula
> Sent: Wednesday, 5 November 2003 7:32
> To: ietf-http-wg@w3.org
> Subject: Relative ordering of fields in HTTP request
> 
> 
> Hi,
> 
> My current understanding is that header fields (say Accept: and
> Connection: ) can fit inside a request header in any order.  
> Is this correct?  If yes, is there a method by which one can 
> enforce that a certain field appear in certain order.
> 
> More generally can the HTTP Server have a say in the ordering 
> of request header fields?
> 
> Thanks,
> Srikanth
> 
Received on Wednesday, 5 November 2003 11:03:34 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:49:25 GMT