REST and Hypermedia: Difference between revisions
Jump to navigation
Jump to search
Line 10: | Line 10: | ||
The content type define by MIME is relevant for HTTP because the | The [[#Media_Type|content type]] define by MIME is relevant for HTTP because the | ||
==Media Type== | ==Media Type== | ||
A '''media type''', also called a '''content type''' or '''MIME type''' is a short string identifying the format of a document. Usually, knowing a document's format allows us to parse it. | A '''media type''', also called a '''content type''' or '''MIME type''' is a short string identifying the format of a document. Usually, knowing a document's format allows us to parse it. |
Revision as of 02:44, 25 September 2018
Internal
Concepts
Multipurpose Internet Mail Extension (MIME)
MIME is an internet standard that extends the format of e-mail to support text in character sets other then ASCII, non-text attachments, such as audio, video, images, application programs, etc., message bodies with multiple parts and header information in non-ASCII characters sets. MIME is specified in six linked RFCs: RFC 2045, RFC 2046, RFC 2047, RFC 4288, RFC 4289 and RFC 2049.
The content type define by MIME is relevant for HTTP because the
Media Type
A media type, also called a content type or MIME type is a short string identifying the format of a document. Usually, knowing a document's format allows us to parse it.