So I dug a little bit into how this stuff works, and I have some questions.

Basically if you answer with the Accept-Range: bytes header, you must be able to receive and process the Range header (event though you can still ignore the Range header).
Basically a client can request things like these (one line = one different request) :

Range: bytes=0-
Range: bytes=200-
Range: bytes=200-1000, 2000-3000, 4000-

First one is dead simple: just send a "File" like we used to do.

Second one is less simple but feasible: Answer with the proper Content-Range, and offset the file by 200 bytes (from a File struct using a Bytes Iterator I guess)

Third one is way less simple, you have to answer something like this according to RFC 2046 :

Content-type: multipart/byteranges; boundary="xxironstaticfileboundaryxx"

--xxironstaticfileboundaryxx
Content-type: application/octet-stream;

200 to 1000 bytes here
--xxironstaticfileboundaryxx
Content-type: application/octet-stream;

2000 to 3000 bytes here...
--xxironstaticfileboundaryxx
Content-type: application/octet-stream;

4000 bytes to end of file here

--xxironstaticfileboundaryxx--

This is technically what we must answer, but unfortunately there is no proper way to answer a multipart body in Iron as of now, so for now I guess I'll pass.

I guess there might also be a way to only reply bytes 200 to 1000, but not only this isn't mentioned as allowed or forbidden in the RFCs, but I don't really know what to answer as well. Do we just answer as if only one range was asked, and we just set the Content-Length and Content-Range accordingly ?

For info, Apache will answer this to a Range: bytes=1000-2000, 3000-4000 request:

Content-Length: 2208
Content-Type: multipart/byteranges; boundary=beb42d06bc54e552

(2208 instead of 2000 is because the delimiter + "Content-type: video/webm" + "Content-range: bytes 3000-4000/29271156" are added as well, twice)

Since we can choose to ignore the "Range" header, I guess we can choose to ignore it when we got more than 1 range as well.

So yeah if someone knows If I can answer only bytes 1000 to 2000 for a request "Range: bytes=1000-2000, 3000-4000", that'd be great.

Support HTTP Byte Serving via Ranges header #93

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions