Print This FAQ

* You Are Here *

6.3.2 RFC 2076 Common Internet Message Headers
6.3.20 RFC 2388 Returning Values from Forms: multipart/form-data
6.3.21 RFC 2376 XML Media Types
6.3.22 RFC 1556 Handling of Bi-directional Texts in MIME
6.3.23 RFC 1524 User Agent Configuration Mechanism For Multimedia Mail Format Information
6.3.24 RFC 1896 MIME text/enriched content-type
6.3.25 RFC 1428 Transition of Internet Mail from Just-Send-8 to 8bit-SMTP/MIME
6.3.26 RFC 1740 MIME Encapsulation of Macintosh Files (MacMIME)
6.3.27 RFC 1741 MIME Content Type for BinHex Encoded Files
6.3.28 RFC 1767 MIME Encapsulation of EDI Objects
6.3.29 RFC 1844 Multimedia E-mail (MIME) User Agent Checklist
6.3.3 RFC 1153 Digest message format
6.3.30 RFC 1864 Content-MD5 Header Field
6.3.31 RFC 2077 The Model Primary Content Type for MIME
6.3.32 RFC 3023 XML Media Types
6.3.4 RFC 1505 Encoding Header Field for Internet Messages
6.3.5 RFC 1049 Content-type header field for Internet messages
6.3.6 RFC 2045 MIME Part 1: Format of Internet Message Bodies
6.3.7 RFC 2046 MIME Part 2: Media Types
6.3.8 RFC 2047 MIME Part 3: Message Header Extensions for Non-ASCII Text
6.3.9 RFC 2048 MIME Part 4: Registration Procedures

6.3.19 RFC 2017 Definition of the URL MIME External-Body Access-Type Printer Friendly Email This FAQ Discuss

http://www.ietf.org/rfc/rfc2017.txt
This memo defines a new access-type for message/external-body MIME parts for Uniform Resource Locators (URLs). URLs provide schemes to access external objects via a growing number of protocols, including HTTP, Gopher, and TELNET. An initial set of URL schemes are defined in RFC 1738.

The formatted version of this faq can be found at http://www.SystemWebMail.com/faq/6.3.19.aspx