Re: patch: reorder headers in query string
On Wed, Mar 12, 2008 at 03:51:24PM +0000, place wrote:
My idea of what seems like a good ordering, for what that's worth :) When I watch the headers, I always wonder why I didn't put Accept-Encoding next to Accept-Charset, for one thing...
AFAIR headers are ordered as they appear in the RFC. I'm not sure whether this is relevant, please check. -- Cheers Jorge.-
Jorge wrote:
On Wed, Mar 12, 2008 at 03:51:24PM +0000, place wrote:
My idea of what seems like a good ordering, for what that's worth :) When I watch the headers, I always wonder why I didn't put Accept-Encoding next to Accept-Charset, for one thing...
AFAIR headers are ordered as they appear in the RFC. I'm not sure whether this is relevant, please check.
Oh! Let's see. The RFC says: 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. Following that, placing them in order of appearance, yields: POST Connection Accept-Charset Accept-Encoding Host Proxy-Authorization Referer User-Agent Content-Length Content-Type Cookie GET Cache-Control Connection Pragma Accept-Charset Accept-Encoding Host Proxy-Authorization Referer User-Agent Cookie Which is pretty close to what dillo has already if you don't count the headers that I have added, since I never realized there was any ordering.
On Wed, Mar 12, 2008 at 07:49:46PM +0000, place wrote:
Jorge wrote:
On Wed, Mar 12, 2008 at 03:51:24PM +0000, place wrote:
My idea of what seems like a good ordering, for what that's worth :) When I watch the headers, I always wonder why I didn't put Accept-Encoding next to Accept-Charset, for one thing...
AFAIR headers are ordered as they appear in the RFC. I'm not sure whether this is relevant, please check.
Oh! Let's see. The RFC says:
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.
Following that, placing them in order of appearance, yields:
POST
Connection
Accept-Charset Accept-Encoding Host Proxy-Authorization Referer User-Agent
Content-Length Content-Type
Cookie
GET
Cache-Control Connection Pragma
Accept-Charset Accept-Encoding Host Proxy-Authorization Referer User-Agent
Cookie
Which is pretty close to what dillo has already if you don't count the headers that I have added, since I never realized there was any ordering.
Thanks for the info. I'd be good to keep the suggested ordering then. -- Cheers Jorge.-
participants (2)
-
jcid＠dillo.org -
place＠gobigwest.com