Mime-type - Revision history

Dan Tobias: Redirect

2017-02-21T00:51:52Z

Redirect

Dan Tobias: Redirect

2017-02-21T00:50:16Z

Redirect

Jsummers: Category:Web

2014-09-19T00:51:10Z

Category:Web

Dan Tobias: /* Sources */

2014-08-23T12:27:44Z

‎Sources

Jsummers at 04:23, 2 March 2013

2013-03-02T04:23:35Z

Dan Tobias at 05:09, 30 December 2012

2012-12-30T05:09:51Z

Dan Tobias at 15:45, 29 December 2012

2012-12-29T15:45:18Z

Dan Tobias at 15:44, 29 December 2012

2012-12-29T15:44:10Z

Dan Tobias at 15:43, 29 December 2012

2012-12-29T15:43:26Z

Dan Tobias at 15:43, 29 December 2012

2012-12-29T15:43:09Z

← Older revision		Revision as of 00:51, 21 February 2017
Line 1:		Line 1:
−	[[~~REDIRECT:~~MIME types]]	+	#REDIRECT[[MIME types]]

@@ Line 1: / Line 1: @@
-{{FormatInfo
+[[REDIRECT:MIME types]]
-|subcat=E-Mail, newsgroups, and forums
-}}
-A '''mime-type''' or '''Internet media type''' is a two-part identifier for [[File Formats|file formats]] on the [[Internet]].
-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.
-−
-==Sources==
-* [[Wikipedia:Internet media type|Wikipedia article]]
-* RFC 2045
-* RFC 2046
-* RFC 4288
-* [http://www.iana.org/assignments/media-types/index.html IANA list of MIME types]
-* [http://mimesniff.spec.whatwg.org/ WHATWG MIME-sniffing standards]
-−
-[[Category:Web]]
-[[Category:Naming and numbering systems]]

@@ Line 2: / Line 2: @@
 |subcat=E-Mail, newsgroups, and forums
 }}
 A '''mime-type''' or '''Internet media type''' is a two-part identifier for [[File Formats|file formats]] on the [[Internet]].
 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.
@@ Line 14: / Line 13: @@
 * [http://mimesniff.spec.whatwg.org/ WHATWG MIME-sniffing standards]
 [[Category:Naming and numbering systems]]

@@ Line 12: / Line 12: @@
 * RFC 4288
 * [http://www.iana.org/assignments/media-types/index.html IANA list of MIME types]
 [[Category:Naming and numbering systems]]

@@ Line 4: / Line 4: @@
 A '''mime-type''' or '''Internet media type''' is a two-part identifier for [[File Formats|file formats]] on the [[Internet]].
-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.
+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.
 ==Sources==

← Older revision		Revision as of 05:09, 30 December 2012
Line 12:		Line 12:
	* RFC 4288		* RFC 4288
	* [http://www.iana.org/assignments/media-types/index.html IANA list of MIME types]		* [http://www.iana.org/assignments/media-types/index.html IANA list of MIME types]
		+
		+	[[Category:Naming and numbering systems]]

@@ Line 3: / Line 3: @@
 }}
-A '''mime-type''' or '''Internet media type''' is a two-part identifier for [[File Format|file format]]s on the [[Internet]].
+A '''mime-type''' or '''Internet media type''' is a two-part identifier for [[File Formats|file formats]] on the [[Internet]].
 The identifiers were originally defined in RFC 2046 for use in email sent through [[Simple Mail Transfer Protocol|SMTP]], but their use has expanded to other protocols such as [[HTTP]], [[Real-time Transport Protocol|RTP]] and [[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.