I think this is due to safari requesting an initial range of bytes 0-1 and the server not truncating the response to the requested end position (it would try returning the whole first blob) - sort of an opposite of the fixed issue with VLC and range start offsets.
I think this is due to safari requesting an initial range of
bytes 0-1
and the server not truncating the response to the requested end position (it would try returning the whole first blob) - sort of an opposite of the fixed issue with VLC and range start offsets.