Return "416 Requested Range Not Satisfiable" instead of "400 Bad Request" #140

New Issue

Closed

opened 2021-11-03 10:26:08 +00:00 by quentin · 0 comments

quentin commented

2021-11-03 10:26:08 +00:00

Owner

If a user asks for an invalid range such as:

Range: bytes=2-1

Other implementations are returning 416 Requested Range Not Satisfiable but we are returning 400 Bad Request.

In practise, it makes debugging more difficult, as it was harder to find people having the same issue as us on Peertube: https://www.reddit.com/r/PeerTube/comments/ofd95d/videos_wont_play_after_transcoding_with_hls/

If a user asks for an invalid range such as: ``` Range: bytes=2-1 ``` Other implementations are returning `416 Requested Range Not Satisfiable` but we are returning `400 Bad Request`. In practise, it makes debugging more difficult, as it was harder to find people having the same issue as us on Peertube: https://www.reddit.com/r/PeerTube/comments/ofd95d/videos_wont_play_after_transcoding_with_hls/