W3C home > Mailing lists > Public > www-talk@w3.org > September to October 2002

Re: Chunking and HTTP/1.1 CLients

From: S. Mike Dierken <mdierken@hotmail.com>
Date: Fri, 25 Oct 2002 08:47:59 -0700
To: "Diwakar Shetty" <Diwakar.Shetty@oracle.com>, <www-talk@w3.org>
Message-ID: <OE413G9Vbj2ltpNebT90000084f@hotmail.com>

It looks like it's support is required and always considered to be
acceptable to a client.

RFC 2616
3.6.1 Chunked Transfer Coding
"All HTTP/1.1 applications MUST be able to receive and decode the "chunked"
transfer-coding, and MUST ignore chunk-extension extensions they do not
understand. "

14.39 TE
"The TE request-header field indicates what extension transfer-codings it is
willing to accept in the response and whether or not it is willing to accept
trailer fields in a chunked transfer-coding. "
[...]
"A server tests whether a transfer-coding is acceptable, according to a TE
field, using these rules:
      1. The "chunked" transfer-coding is always acceptable. [...] "



----- Original Message -----
From: "Diwakar Shetty" <Diwakar.Shetty@oracle.com>
To: <www-talk@w3.org>
Sent: Friday, October 25, 2002 7:42 AM
Subject: Chunking and HTTP/1.1 CLients


>
>
>
> Is it a "MUST" requirement for HTTP/1.1 clients to support chunking ??
>
> Or Is the chunking capability to be advertised by the client before the
> server can send chunked encoded response ?
> If yes, then which header is used for that (by the client to advertise
> capability) ?
> I know the server sends "Transfer-Encoding: chunked" header in the
> response
>
> Thanks in advance for all your replies
>
> Diwakar
>
Received on Friday, 25 October 2002 12:00:18 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 27 October 2010 18:14:27 GMT