We still have the issue that 406 streaming responses have their last bunch of chunks being sent with a [416] Content-Range is not specified! error. The file is playable and it does not affect users (to our current knowledge) but it indicates an error in the implementation.
We still have the issue that 406 streaming responses have their last bunch of chunks being sent with a
[416] Content-Range is not specified!error. The file is playable and it does not affect users (to our current knowledge) but it indicates an error in the implementation.