Bug 236796

Summary: Range requests to objectURL results in a 416 status and failed video playback
Product: WebKit Reporter: Adam Podolnick <adam>
Component: MediaAssignee: Nobody <webkit-unassigned>
Status: RESOLVED DUPLICATE    
Severity: Critical CC: jer.noble, mjs, webkit-bug-importer
Priority: P2 Keywords: InRadar
Version: Safari 15   
Hardware: iPhone / iPad   
OS: iOS 15   
Attachments:
Description Flags
Test Case
none
15.3 does not send Range header
none
15.4 adds a Range header resulting in a 416 none

Description Adam Podolnick 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?
Comment 1 Adam Podolnick 2022-02-17 12:14:45 PST
Created attachment 452403 [details]
15.3 does not send Range header
Comment 2 Adam Podolnick 2022-02-17 12:15:20 PST
Created attachment 452404 [details]
15.4 adds a Range header resulting in a 416
Comment 3 Sam Sneddon [:gsnedders] 2022-02-17 14:48:59 PST
I presume, from your email, this is affecting at least some https://sproutvideo.com hosted videos?
Comment 4 Radar WebKit Bug Importer 2022-02-17 14:49:10 PST
<rdar://problem/89110139>
Comment 5 Adam Podolnick 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.
Comment 6 Maciej Stachowiak 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 ***