[wp-trac] [WordPress Trac] #42560: mp4 files do not play in Safari

[WordPress Trac]

#42560: mp4 files do not play in Safari
--------------------------+------------------------------
 Reporter:  cg923         |       Owner:
     Type:  defect (bug)  |      Status:  reopened
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Media         |     Version:  3.0
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:  multisite
--------------------------+------------------------------
Changes (by dd32):

 * focuses:   => multisite
 * version:  4.8.3 => 3.0


Comment:

 Replying to [comment:8 blobfolio]:
 > I completely forgot about the legacy file-serving feature for older
 network sites!

 For reference, we disabled it by default in WordPress 3.5 / #19235 (5
 years ago), since then ms-files.php has had very little work done on it,
 quite a few tickets are still hanging around which are realistically never
 going to be fixed - this included IMHO.

 Instead of adding support for the `Range` header, I'm curious if instead
 we can simply respond to the request with a `Do not support` response
 instead to force Safari into some other mode. Upon looking into it, that's
 what we currently do by returning a `200 OK` response (according to
 https://tools.ietf.org/html/rfc7233#section-4.4) but it appears that
 possibly unfortunately Safari is buggy and doesn't support a fallback,
 maybe there's another response we can make to trigger Safari in that
 scenario?

 Personally I'm inclined to say `wontfix` based on this being a new
 enhancement to a feature we deprecated quite some time ago, and it only
 being triggered by a browser failing to operate correctly. The the impact
 this has upon legacy networks isn't exactly small though, and moving a
 legacy network to not use ms-files.php may not be straight forward either
 (I honestly do not know if simply changing the option is enough) which is
 why adding support here may not be the worst idea.

 ----

 An additional testing requirement: What versions of Safari trigger this
 issue? latest version? or just old versions? Is there a webkit bug # known
 for it?

--
Ticket URL: <https://core.trac.wordpress.org/ticket/42560#comment:11>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform