Add support for "Range" header for Large Media files

This allows fetching only a small part of the file. Sometimes files are big and I don’t need to download the whole file just to get some small part of it. With Range header, you can specify the range of bytes you want to download.

See for request header:

See for response header:

1 Like

Hi there,

I’ve added your voice to the open feature request on this topic so we can let you know if we implement it. I don’t anticipate that the functionality there will change anytime soon, though.

1 Like

Would love this feature too, for hosting podcasts.

This appears to be required by the latest Safari for playing files via audio. What’s annoying is sometimes requests for files like .mp3 return 206 Partial Content header and sometimes it just returns a 200 OK.

@fool Is the development team actively testing something in production? Is that why this behavior is so sporadic?

@brettbuddin, as far as I know, no one is testing changes to this in production.

Would be willing to send us the x-nf-request-id headers for similar requests which return the two different (200 and 206) status codes for the same resource?

If this can be reproduced in a browser and can captured as HAR file, that would also be very helplful.