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

#343: chunk-extensions

From: Mark Nottingham <mnot@mnot.net>
Date: Wed, 8 Feb 2012 06:46:20 +1100
Message-Id: <B14486FA-D8C3-4DD7-A100-8C8325F9D3D8@mnot.net>
To: HTTP Working Group <ietf-http-wg@w3.org>
Now <http://trac.tools.ietf.org/wg/httpbis/trac/ticket/343>.


On 07/02/2012, at 12:03 PM, Mark Nottingham wrote:

> Right now, this is all we say about chunk-extensions (beyond the BNF, etc.):
> 
>>   All HTTP/1.1 applications MUST be able to receive and decode the
>>   "chunked" transfer-coding and MUST ignore chunk-ext extensions they
>>   do not understand.
> 
> Since this is an extensibility point, we should give guidance on how it should be used. 
> 
> I can't really see establishing a chunk-extension registry; they don't have any semantic, and AFAIK haven't really been used in anger.
> 
> What do people think about adding advice along these lines:
> 
> """
> Use of chunk-extensions by senders is deprecated; they SHOULD NOT be sent and definition of new chunk-extensions is discouraged.
> """
> 
> ?
> 
> --
> Mark Nottingham   http://www.mnot.net/
> 
> 
> 
> 

--
Mark Nottingham   http://www.mnot.net/
Received on Tuesday, 7 February 2012 19:52:26 GMT

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