RESOLVED DUPLICATE of bug 236401236796
Range requests to objectURL results in a 416 status and failed video playback
https://bugs.webkit.org/show_bug.cgi?id=236796
Summary Range requests to objectURL results in a 416 status and failed video playback
Adam Podolnick
Reported 2022-02-17 12:12:46 PST
Created attachment 452402 [details] Test Case Safari seems to be making range requests when making requests to object URLs that are used as sources for a video element. Prior to 15.4, Safari would not add a Range header to the request. Now it is adding a Range: bytes=0-* header to the request which results in a 416 error status causing video playback to fail on iPhone and iPad. I've attached a test case that shows the unexpected behavior. Was this change intentional? If so, are there workarounds?
Attachments
Test Case (908 bytes, text/html)
2022-02-17 12:12 PST, Adam Podolnick
no flags
15.3 does not send Range header (42.05 KB, image/png)
2022-02-17 12:14 PST, Adam Podolnick
no flags
15.4 adds a Range header resulting in a 416 (45.46 KB, image/png)
2022-02-17 12:15 PST, Adam Podolnick
no flags
Adam Podolnick
Comment 1 2022-02-17 12:14:45 PST
Created attachment 452403 [details] 15.3 does not send Range header
Adam Podolnick
Comment 2 2022-02-17 12:15:20 PST
Created attachment 452404 [details] 15.4 adds a Range header resulting in a 416
Sam Sneddon [:gsnedders]
Comment 3 2022-02-17 14:48:59 PST
I presume, from your email, this is affecting at least some https://sproutvideo.com hosted videos?
Radar WebKit Bug Importer
Comment 4 2022-02-17 14:49:10 PST
Adam Podolnick
Comment 5 2022-02-17 15:02:18 PST
(In reply to Sam Sneddon [:gsnedders] from comment #3) > I presume, from your email, this is affecting at least some > https://sproutvideo.com hosted videos? Hi, Sam! That's correct. This affects videos hosted on sproutvideo.com.
Maciej Stachowiak
Comment 6 2022-02-18 00:41:57 PST
According to info in the radar, this is a dupe of https://bugs.webkit.org/show_bug.cgi?id=236401 (which is already fixed on mainline) *** This bug has been marked as a duplicate of bug 236401 ***
Note You need to log in before you can comment on or make changes to this bug.