Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>This is a convention defined in <a href="http://tools.ietf.org/html/rfc2045#section-5.1" rel="noreferrer" title="RFC 2045 - Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies - Section 5.1: Syntax of the Content-Type Header Field">RFC 2045 - Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies</a>.</p> <blockquote> <ol> <li><p>Private <em>[subtype]</em> values (starting with "X-") may be defined bilaterally between two cooperating agents without outside registration or standardization. Such values cannot be registered or standardized.</p></li> <li><p>New standard values should be registered with IANA as described in <a href="http://tools.ietf.org/html/rfc2048" rel="noreferrer">RFC 2048</a>.</p></li> </ol> </blockquote> <p>A similar restriction applies to the top-level type. From the same source,</p> <blockquote> <p>If another top-level type is to be used for any reason, it must be given a name starting with "X-" to indicate its non-standard status and to avoid a potential conflict with a future official name.</p> </blockquote> <p><em>(Note that per RFC 2045, "[m]atching of media type and subtype is ALWAYS case-insensitive", so there's no difference between the interpretation of 'X-' and 'x-'.)</em></p> <p>So it's fair to guess that "application/x-foo" was used before the IANA defined "application/foo". And it still might be used by folks who aren't aware of the IANA token assignment.</p> <p>As Chris Hanson said MIME types are controlled by the IANA. This is detailed in <a href="http://tools.ietf.org/html/rfc2048" rel="noreferrer" title="RFC 2048 - Internet Mail Extensions (MIME) Part Four: Registration Procedures">RFC 2048 - Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures</a>. According to <a href="http://tools.ietf.org/html/rfc3778#section-2" rel="noreferrer" title="RFC 3778: The application/pdf Media Type - Section 2: History">RFC 3778</a>, which is <a href="http://www.iana.org/assignments/media-types/application/" rel="noreferrer" title="IANA - Application Media Types">cited by the IANA</a> as the definition for "application/pdf",</p> <blockquote> <p>The application/pdf media type was first registered in 1993 by Paul Lindner for use by the gopher protocol; the registration was subsequently updated in 1994 by Steve Zilles.</p> </blockquote> <p>The type "application/pdf" has been around for well over a decade. So it seems to me that wherever "application/x-pdf" has been used in new apps, the decision may not have been deliberate.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload