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

RE: Range Responses of Indeterminate Length: Draft

From: <K.Morgan@iaea.org>
Date: Tue, 13 Oct 2015 08:57:25 +0000
To: <rodger.combs@gmail.com>, <ietf-http-wg@w3.org>
CC: <mnot@mnot.net>
Message-ID: <0356EBBE092D394F9291DA01E8D28EC201D254E3ED@SEM002PD.sg.iaea.org>
On Friday,02 October 2015 02:28, rodger.combs@gmail.com<mailto:rodger.combs@gmail.com> wrote:
>

> I've updated https://datatracker.ietf.org/doc/draft-combs-http-indeterminate-range/


> to address some minor formatting issues, and complete the IANA Considerations section.

> Does anyone have any input on this?



Sorry for the late and possibly ignorant response. Is what you’re trying to accomplish already possible with the use of multipart/byteranges?



e.g.

- Client requests stream starting from byte 0 of an unknown length.

- Server responds in N-KByte buffers (e.g. 1K) of data from a stream of unknown length (chunking not shown for brevity)

- Response ends at the end of stream or when the client closes the connection to seek to a new location





GET /path/file HTTP/1.1

Host: example.com

Range: bytes=0-





HTTP/1.1 206 Partial Content

Date: Wed, 15 Nov 1995 06:25:24 GMT

Last-Modified: Wed, 15 Nov 1995 04:58:08 GMT

Transfer-Encoding: chunked

Content-Type: multipart/byteranges; boundary=THIS_STRING_SEPARATES



--THIS_STRING_SEPARATES

Content-Type: file/mimetype

Content-Range: bytes 0-1023/*



...the first range...

--THIS_STRING_SEPARATES

Content-Type: file/mimetype

Content-Range: bytes 1024-2047/*



...the second range...

--THIS_STRING_SEPARATES—

...





-keith



This email message is intended only for the use of the named recipient. Information contained in this email message and its attachments may be privileged, confidential and protected from disclosure. If you are not the intended recipient, please do not read, copy, use or disclose this communication to others. Also please notify the sender by replying to this message and then delete it from your system.
Received on Tuesday, 13 October 2015 08:58:04 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 11:11:39 UTC