[wp-trac] [WordPress Trac] #39963: MIME Alias Handling

[WordPress Trac]

#39963: MIME Alias Handling
--------------------------------------+-----------------------------
 Reporter:  blobfolio                 |       Owner:
     Type:  enhancement               |      Status:  reopened
 Priority:  normal                    |   Milestone:  5.0
Component:  Media                     |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:  administration
--------------------------------------+-----------------------------
Changes (by joemcgill):

 * status:  closed => reopened
 * resolution:  wontfix =>
 * milestone:   => 5.0


Comment:

 After thinking about this for a while now, I want to take another look at
 adding MIME aliasing. A few concerns that I'd want us to look into:

 1. Let's make sure there is a solid plan for keeping the MIME database up
 to date so things don't go stale.
 2. I'm curious if we could limit the (massive) list in
 [attachment:mimes.3.diff] to only include mimes that are currently
 supported by WordPress, while allowing the list to be extended to a more
 full list for plugins that want to provide that functionality, but that's
 not a blocker.
 3. I like the idea of putting application/octet stream MIMES through an
 extra set of checks, similarly to what is proposed in #40175, but we may
 need to read the first few bytes of files ourselves rather than relying on
 an external library, like fileinfo.

 I'd also like to get feedback from folks at larger hosting companies or
 from WP.com, who have had to add additional checking around MIMES.
 @mikeschroder, I'd appreciate your feedback there.

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