[Webkit-unassigned] [Bug 221622] [GStreamer] Cannot play mp4 videos in Element: Received unexpected 200 HTTP status code for range request

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=221622

Philippe Normand <pnormand at igalia.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
                 CC|                            |pnormand at igalia.com
         Resolution|INVALID                     |---

--- Comment #4 from Philippe Normand <pnormand at igalia.com> ---
Reading this: https://tools.ietf.org/id/draft-ietf-httpbis-p5-range-09.html#header.content-range

If the server ignores a byte-range-spec because it is syntactically invalid, the server SHOULD treat the request as if the invalid Range header field did not exist. (Normally, this means return a 200 response containing the full entity).

If the server receives a request (other than one including an If-Range request-header field) with an unsatisfiable Range request-header field (that is, all of whose byte-range-spec values have a first-byte-pos value greater than the current length of the selected resource), it SHOULD return a response code of 416 (Requested range not satisfiable) (Section 3.2).

Note: Clients cannot depend on servers to send a 416 (Requested range not satisfiable) response instead of a 200 (OK) response for an unsatisfiable Range request-header, since not all servers implement this request-header.

... So, do I understand correctly that we should expect 200 (OK) when the server wasn't able to fullfil the range request?

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20210910/863fd23f/attachment.htm>