- From: Martin Thomson <martin.thomson@gmail.com>
- Date: Fri, 4 Oct 2013 17:07:10 -0700
- To: Osama Mazahir <OSAMAM@microsoft.com>
- Cc: HTTP Working Group <ietf-http-wg@w3.org>
On 4 October 2013 16:24, Osama Mazahir <OSAMAM@microsoft.com> wrote: > Section 4.1 in draft-ietf-httpbis-p5-range-24 has the following example: HEADERS > 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 > Content-Length: 1741 > Content-Type: multipart/byteranges; boundary=THIS_STRING_SEPARATES END_HEADERS DATA > --THIS_STRING_SEPARATES > Content-Type: application/pdf > Content-Range: bytes 500-999/8000 > > ...the first range... > --THIS_STRING_SEPARATES > Content-Type: application/pdf > Content-Range: bytes 7000-7999/8000 > > ...the second range > --THIS_STRING_SEPARATES-- END_STREAM > So the above example would translate into a HEADERS frame (+END_HEADERS) covering the first set of headers (e.g. date, last-modified, content-length, content-type) and then everything thereafter (separators, "Content-Type: application/pdf", content-range, binary data, etc) would be wrapped into a DATA frame? Yep. The content-type is multipart/byteranges;... . The content starts at the first '--' + boundary and ends at the last '--' + boundary + '--', all of which gets carried in DATA frames.
Received on Saturday, 5 October 2013 00:07:38 UTC