Hi.
I’m wondering whether you have any further on this issue. I’m facing the same issue and seeking to debug it in the dev console but with limited success.
It would be good to confirm my assumptions about what the viewer is expecting in order to use byte range support. It looks to me like the requirement is for the site to return the following headers:
- Content-Encoding: “identity” or not supplied
- Accept-Ranges: “bytes”
- Content-Length: Must return an value parsable by parseInt that is a number.
Plus the content length header’s value must be > 2 x the chunk size and you must be using http/https as the URL protocol.
There also seems to be support for disabling the use of ranges and setting the range size, but I haven’t spent the time to figure out whether/how they can be configured.