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 12:57:35 -0600
Message-ID: <CACuKZqEAgQS+pJMtroY+Ogn+RSe3djRcCkSTCBkhkQUm43J2fA@mail.gmail.com>
To: Duncan Cragg <duncan@cilux.org>
Cc: ietf-http-wg@w3.org
The categorization of headers is indeed very confusing; here's my take
(not an expert)

    request and response

    request and response

    However, HTTP/1.1 only really described it for responses to GET requests.
    its meaning in other contexts is unclear.

    request and response

    However, there's no official way for client to know what encoding is
    acceptable by server; a request with Content-Encoding is risky.

    request and response

    response only.
    (It applies to the representation/entity, not the response)

    response only;
    and it applies to the response! not the representation/entity.

    response only;
    applies to the representation/entity

    request and response
    However, it doesn't seem to be very useful in requests

    request and response
    However, usage of Content-Language in requests is not elaborated.

So basically, only headers that are appropriate in requests are
Content-Length/Transfer-Encoding, Content-Type.

Zhong Yu
Received on Wednesday, 18 January 2012 18:58:10 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 11:11:00 UTC