[Webkit-unassigned] [Bug 202019] New: Video Element Progressive Download of MP4 Makes Poorly Behaved Network Requests

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu Sep 19 19:06:09 PDT 2019


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

            Bug ID: 202019
           Summary: Video Element Progressive Download of MP4 Makes Poorly
                    Behaved Network Requests
           Product: WebKit
           Version: Safari 12
          Hardware: All
                OS: macOS 10.14
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Media
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: mcfa0086 at umn.edu

Created attachment 379186

  --> https://bugs.webkit.org/attachment.cgi?id=379186&action=review

Inspector showing the range requests

We vend MP4 video from AWS S3 buckets, which are displayed using a standard <video> element.  WebKit initially buffers a sizable amount of video from the server, and then closes the connection.  When it needs to load additional data (as playback progresses), it makes a 206 Partial Content request with a Content-Range requesting the entire remainder of the file.  After loading a small amount of data (roughly 2 megabytes in our environment), the connection is aborted.  

Because the content-range request asked for the entire remainder of the file, and because the connection was aborted, this causes excessive billing and data transfer on the server side.  In our environment with AWS S3, a connection in which the WebKit client loads ~2 megabytes will incur ~12 megabytes of billed data.

Ideally would set the content-range more accurately according to the data it actually intends to load, or would maintain a single long-running connection to the server (this is the current behavior in Chrome). 

I can provide a test environment if necessary, but would rather not do so publicly as the testing process could expose us to substantial costs.

-- 
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/20190920/3ee9d728/attachment.html>


More information about the webkit-unassigned mailing list