MIME types - Revision history

Jsummers at 15:39, 2 October 2017

2017-10-02T15:39:48Z

Dan Tobias: Merge info from old page and new one

2017-02-21T00:53:54Z

Merge info from old page and new one

Arlo James Barnes: Got it this time, colon before

2017-02-20T23:37:31Z

Got it this time, colon before

Arlo James Barnes: Not sure how to link a category without applying it

2017-02-20T23:35:33Z

Not sure how to link a category without applying it

Arlo James Barnes: Almost as important as magic numbers and extensions

2017-02-20T23:34:02Z

Almost as important as magic numbers and extensions

New page

Multipurpose Internet Mail Extensions file type designators, commonly shortened to '''MIME types''', and formally called [[media type]]s to reflect that their usage has grown beyond identifying email attachments, are a handy way to refer to file formats. IANA hands them out upon request/review.

[[Template:Mimetype]]
[[Category:FormatInfo without mimetypes]]

@@ Line 2: / Line 2: @@
 |subcat=E-Mail, newsgroups, and forums
 }}
-'''Multipurpose Internet Mail Extensions''' file type designators, commonly shortened to '''MIME types''', and formally called [[media type]]s to reflect that their usage has grown beyond identifying email attachments, are a handy way to refer to file formats. IANA hands them out upon request/review. The identifiers were originally defined in RFC 2046 for use in email sent through [[SMTP]], but their use has expanded to other protocols such as [[HTTP]], [[Real-time Transport Protocol|RTP]] and [[Session Initiation Protocol|SIP]]. These types were called '''MIME types''', and are sometimes referred to as '''Content-types''', after the name of a header in several protocols whose value is such a type. The original name '''MIME type''' referred to usage to identify non-ASCII parts of email messages composed using the [[MIME]] (Multipurpose Internet Mail Extensions) specification. Without MIME types, email clients would not be able to understand if an attachment file were a graphics file or a spreadsheet etc. and would not be able to handle the attachment appropriately.
+'''Multipurpose Internet Mail Extensions''' file type designators, commonly shortened to '''MIME types''', and formally called [[media type]]s to reflect that their usage has grown beyond identifying email attachments, are a handy way to refer to file formats. IANA hands them out upon request/review. The identifiers were originally defined in RFC 2046 for use in email sent through [[SMTP]], but their use has expanded to other protocols such as [[HTTP]], [[RTP]] and [[Session Initiation Protocol|SIP]]. These types were called '''MIME types''', and are sometimes referred to as '''Content-types''', after the name of a header in several protocols whose value is such a type. The original name '''MIME type''' referred to usage to identify non-ASCII parts of email messages composed using the [[MIME]] (Multipurpose Internet Mail Extensions) specification. Without MIME types, email clients would not be able to understand if an attachment file were a graphics file or a spreadsheet etc. and would not be able to handle the attachment appropriately.
 ==Sources==

@@ Line 1: / Line 1: @@
-Multipurpose Internet Mail Extensions file type designators, commonly shortened to '''MIME types''', and formally called [[media type]]s to reflect that their usage has grown beyond identifying email attachments, are a handy way to refer to file formats. IANA hands them out upon request/review.
+{{FormatInfo
 [[Template:Mimetype]]
 [[:Category:FormatInfo without mimetypes]]

← Older revision		Revision as of 23:37, 20 February 2017
Line 2:		Line 2:

	[[Template:Mimetype]]		[[Template:Mimetype]]
−	[[~~Category~~:~~FormatInfo without mimetypes\|~~Category:FormatInfo without mimetypes]]	+	[[:Category:FormatInfo without mimetypes]]

← Older revision		Revision as of 23:35, 20 February 2017
Line 2:		Line 2:

	[[Template:Mimetype]]		[[Template:Mimetype]]
−	[[Category:FormatInfo without mimetypes]]	+	[[Category:FormatInfo without mimetypes\|Category:FormatInfo without mimetypes]]