Mime-types 1.24 Released

Ruby
1

mime-types version 1.24 has been released!

This library allows for the identification of a file’s likely MIME
content
type. This is release 1.24, adding and updating a few MIME types and
fixing
some issues with documentation.

MIME types are used in MIME-compliant communications, as in e-mail or
HTTP
traffic, to indicate the type of content which is transmitted.
MIME::Types
provides the ability for detailed information about MIME entities
(provided as
a set of MIME::Type objects) to be determined and used programmatically.
There
are many types defined by RFCs and vendors, so the list is long but not
complete; don’t hesitate to ask to add additional information. This
library
follows the IANA collection of MIME types (see below for reference).

MIME::Types for Ruby was originally based on MIME::Types for Perl by
Mark
Overmeer, copyright 2001 - 2009. As of version 1.15, the data format for
the
MIME::Type list has changed and the synchronization will no longer
happen.

MIME::Types is built to conform to the MIME types of RFCs 2045 and 2231.
It
tracks the {IANA registry}[Media Types]
({ftp}[ftp://ftp.iana.org/assignments/media-types]) with some unofficial
types
added from the {LTSW
collection}[http://www.ltsw.se/knbase/internet/mime.htp]
and added by the users of MIME::Types.

Changes:

1.24 / 2013-08-14

  • Code Climate:
  • Documentation:
    • LeoYoung [email protected] pointed out that the README.rdoc
      contained
      examples that could never possibly work because MIME::Types#[]
      returns (for
      all the versions I have handy) an array, not a single type. I have
      updated
      README.rdoc to reflect this.
  • Removed Nokogiri as a declared development dependency. It is still
    required
    if you’re going to use the IANA parser functionality, but it is not
    necessary
    for most development purposes. This has been removed to ensure that
    Travis CI
    passes on Ruby 1.8.7.
  • New MIME Types:
  • Updated MIME Types:
    • RFC 6960 was adopted (application/ocsp-request and
      application/ocsp-response).