W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2002

RE: content-encoding and range headers

From: Julian Reschke <julian.reschke@gmx.de>
Date: Tue, 10 Dec 2002 16:20:50 +0100
To: "Scott Lawrence" <lawrence@world.std.com>, "Stefan Eissing" <stefan.eissing@greenbytes.de>
Cc: <ietf-http-wg@w3.org>
Message-ID: <JIEGINCHMLABHJBIGKBCOEGJFPAA.julian.reschke@gmx.de>

> From: ietf-http-wg-request@w3.org [mailto:ietf-http-wg-request@w3.org]On
> Behalf Of Scott Lawrence
> Sent: Tuesday, December 10, 2002 3:34 PM
> To: Stefan Eissing
> Cc: ietf-http-wg@w3.org
> Subject: Re: content-encoding and range headers
> 
> 
> 
> Stefan Eissing <stefan.eissing@greenbytes.de> writes:
> 
> > My understanding of 2616 is that range is applied to the
> > content-encoded entity. So if an entity is gzipped, the
> > byte selection is applied on the gzipped representation.
> 
> I don't believe that this is correct.  The Range specifies bytes in
> the 'entity'; the Content-Encoding refers to a coding method
> _applied_to_ the 'entity', so the Content-Range header would refer to
> the bytes in the original entity, and the Content-Encoding describes
> how that has been encoded to create the message body.
> ...

I agree that it depends on the definition of the entity body, which is [1]:

	entity-body := Content-Encoding( Content-Type( data ) )

So I think Stefan's analysis is correct...



[1] <http://greenbytes.de/tech/webdav/rfc2616.html#rfc.section.7.2.1>


--
<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760 
Received on Tuesday, 10 December 2002 10:21:46 GMT

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