Subject: ranges and chunked encoding

From: Doug Moore <[email-masked]>
Date: Sat, 24 May 2008 22:21:44 +0000

A comment.

Forming a single range response for a client based on
a chunk-encoded response from a server is quite
challenging.  The response size cannot be determined
until delivery from server is complete, so a response
header for client cannot be completed until then.  A
multirange response is also demanding.

I'd like to see a transfer-encoding based alternative
to Content-Range.  Something like:

Transfer-Range: bytes = 1000

or, without introduce a new header, just

Content-Range: bytes = 1000-*/*

implying a transfer encoding for the next range.

Any way that can happen, someday?

Doug Moore