RFC 2068:Hypertext Transfer Protocol -- HTTP/1.1
RFC-Ref

internet mail


Click on the red underlined text to get to the source

... method is to be applied. Messages are passed in a format similar to that used by Internet mail as defined by the Multipurpose Internet Mail Extensions (MIME ...
... applied. Messages are passed in a format similar to that used by Internet mail as defined by the Multipurpose Internet Mail Extensions (MIME). ...


... specification will help reduce past confusion over the relationship between HTTP and Internet mail message formats. The HTTP ...


... Freed, N., and N. Borenstein, "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies", RFC 2045draft ...
... Moore, K., "MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text", RFC 2047draft ...


... HTTP/1.1 uses many of the constructs defined for Internet Mail (RFC 822) and the Multipurpose Internet Mail Extensions (MIME ...
... HTTP/1.1 uses many of the constructs defined for Internet Mail (RFC 822) and the Multipurpose Internet Mail Extensions (MIME ) to allow entities to be transmitted in an open variety of representations and ...
... MIME requires that an Internet mail entity be converted to canonical form prior to being transferred. Section 3.7.1 of this document ...
... experimental applications of Content-Type for Internet mail have used a media-type parameter of ";conversions=<content-coding>" to perform an equivalent ...



Google
Web
RFC-Ref