W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > April to June 2006

Re: getcontentlength property

From: Julian Reschke <julian.reschke@gmx.de>
Date: Tue, 09 May 2006 10:08:46 +0200
Message-ID: <44604E0E.9090409@gmx.de>
To: WebDAV <w3c-dist-auth@w3.org>
CC: werner.donne@re.be

Julian Reschke wrote:
> 
> Werner Donné wrote:
>> Hi,
>>
>> RFC 2518 says that the getcontentlength property is mandatory if
>> the resource returns the Content-Length header in response to a GET.
>>
>> In a servlet container you don't always know if that header will
>> be in the response. Normally a document is streamed to the response
>> body. The container sees this because of the intermediate flushes.
>> It will then use the chunked transfer encoding. It can be, however,
>> that the document is smaller than the internal streaming buffer.
>> There are no intermediate flushes then and the container may choose
>> to not use a transfer encoding, in which case the Content-Length
>> header will be set.
>>
>> It is also an expensive operation if the document is versioned and
>> must be reconstructed from a delta file.
> 
> Agreed, there are cases where a WebDAV server implementor simply doesn't 
> have any control over this. Therefore the MUST level requirement should 
> be relaxed to a SHOULD.
> 
> Best regards, Julian
> 
> (cc:ing the WebDAV WG mailing list, because this happens not to be a 
> Versioning question)

Added as issue to BugZilla: 
<http://ietf.cse.ucsc.edu:8080/bugzilla/show_bug.cgi?id=239>.

Best regards, Julian
Received on Tuesday, 9 May 2006 09:52:08 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:44:14 GMT