Re: estimated Content-Length with chunked encoding

Greg Dean wrote:
> I am new to this mailing list.  I wanted to bounce an idea that I’ve had 
> for a while off everyone/anyone.  Basically I’d like to provide the 
> sender of a chunked encoding message to indicate an estimate of the 
> content.  In the following example resource.zip is created dynamically, 
> however the approximate size is known.
> 
>  
> 
> C: Get /resource.zip HTTP/1.1
> 
>  
> 
> S: HTTP/1.1 200 OK
> 
> S: Transfer-Encoding: chunked
> 
> S: Estimated-Content-Length: 300000
> ...

Interesting enough, the MacOS X WebDAV Client already seems to use 
something like that:

> C-68-#000000 -> [PUT /content/dam/STROMBERG_2_2.mp4 HTTP/1.1 ]
> C-68-#000045 -> [User-Agent: WebDAVFS/1.7 (01708000) Darwin/9.5.1 (i386) ]
> C-68-#000102 -> [Accept: */* ]
> C-68-#000115 -> [X-Expected-Entity-Length: 302108459 ]
> C-68-#000152 -> [If: (<3ef131eb-eb74-47a4-ae97-a72d94ee6ac9-1>) ]
> C-68-#000200 -> [Authorization: Basic YWRtaW46YWRtaW4= ]
> C-68-#000239 -> [Connection: close ]
> C-68-#000258 -> [Host: localhost:1234 ]
> C-68-#000280 -> [Transfer-Encoding: Chunked ]
> C-68-#000308 -> [ ]
> C-68-#000310 -> [800 ]

(see 
<https://issues.apache.org/jira/browse/JCR-1837?focusedCommentId=12642918#action_12642918>)

BR, Julian

Received on Monday, 27 October 2008 14:44:04 UTC