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

Closed
opened 11 months ago by quentin · 0 comments
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/
quentin added the
Newcomer
S3 Compatibility
labels 11 months ago
lx referenced this issue from a commit 10 months ago
lx closed this issue 10 months ago
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.