W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2012

Re: Defining the meaning of headers associated with a request body

From: Zhong Yu <zhong.j.yu@gmail.com>
Date: Wed, 18 Jan 2012 14:19:59 -0600
Message-ID: <CACuKZqFoj2sgQwovkN4MaW8h9vPM+iB7tZFwT_bup2PrUVq7dg@mail.gmail.com>
To: Karl Dubost <karld@opera.com>
Cc: Duncan Cragg <duncan@cilux.org>, ietf-http-wg@w3.org
On Wed, Jan 18, 2012 at 1:43 PM, Karl Dubost <karld@opera.com> wrote:
> A long long long time ago, when elves were still existing, there was a nice page about
>
> HTTP headers for Request
> http://www.w3.org/Protocols/HTTP/HTRQ_Headers.html
>
> HTTP headers for Response
> http://www.w3.org/Protocols/HTTP/Object_Headers.html
>
>
> In a more recent document ;) this still exists
>
> 3.2.  Request Header Fields
> http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-18#section-3.2
>
> 3.3.  Response Header Fields
> http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-18#section-3.3
>

But they are not very consistent. For example, how come Expires is a
representation header, not a response header, while ETag is a response
header, not a representation header?

>
> PS: /me loves the "Cost:" header. :)
> http://www.w3.org/Protocols/HTTP/Object_Headers.html#cost

We still have 402 Payment Required :)

>
>
> --
> Karl Dubost - http://dev.opera.com/
> Developer Relations, Opera Software
>
Received on Wednesday, 18 January 2012 20:20:39 GMT

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