[wp-meta] [Making WordPress.org] #587: Invalid MIME Type at ps.w.org

[Making WordPress.org]

#587: Invalid MIME Type at ps.w.org
--------------------------+-------------------------------
  Reporter:  extendwings  |      Owner:
      Type:  defect       |     Status:  new
  Priority:  normal       |  Component:  Plugins Directory
Resolution:               |   Keywords:
--------------------------+-------------------------------

Comment (by Otto42):

 The mime type is set by the client, typically, and this information is
 stored on the server. The SVN server will read the svn:mime-type property
 and server it using that mime-type.

 Now, while we recently made a change to the svn system to serve things
 with an automatic mime-type, I suspect that if the svn:mime-type is
 incorrectly set, then it will cause the system to override this. The
 ps.w.org CDN is simply mirroring that information.

 In short, http://plugins.svn.wordpress.org/akismet/assets/icon-256x256.png
 has an svn:mime-type property set to application/octet-stream, while
 http://plugins.svn.wordpress.org/jetpack/assets/screenshot-1.png has its
 svn:mime-type set to image/png.

 Note that http://plugins.svn.wordpress.org/jetpack/assets/icon-256x256.png
 has an svn:mime-type of application/octet-stream too, so I suspect that
 whatever client is being used to check in these files is forcing the svn
 :mime-type property here.

 The fix is simple and detailed in this blog post:
 http://make.wordpress.org/plugins/2014/03/20/plugin-screenshots-
 downloading/

 I think this is client dependent and we may want to force automatic mime-
 types all around somehow, but we'll need to investigate that. For the time
 being, plugin authors do have ultimate control over their mime-types and
 should set them correctly, or at least, not set them incorrectly.

--
Ticket URL: <https://meta.trac.wordpress.org/ticket/587#comment:1>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org