Connected: An Internet Encyclopedia
19.4.7 MIME-Version

Up: Connected: An Internet Encyclopedia
Up: Requests For Comments
Up: RFC 2068
Up: 19 Appendices
Up: 19.4 Differences Between HTTP Entities and MIME Entities
Prev: 19.4.6 Introduction of Transfer-Encoding
Next: 19.5 Changes from HTTP/1.0

19.4.7 MIME-Version

19.4.7 MIME-Version

HTTP is not a MIME-compliant protocol (see appendix 19.4). However, HTTP/1.1 messages may include a single MIME-Version general-header field to indicate what version of the MIME protocol was used to construct the message. Use of the MIME-Version header field indicates that the message is in full compliance with the MIME protocol. Proxies/gateways are responsible for ensuring full compliance (where possible) when exporting HTTP messages to strict MIME environments.

          MIME-Version   = "MIME-Version" ":" 1*DIGIT "." 1*DIGIT

MIME version "1.0" is the default for use in HTTP/1.1. However, HTTP/1.1 message parsing and semantics are defined by this document and not the MIME specification.


Next: 19.5 Changes from HTTP/1.0

Connected: An Internet Encyclopedia
19.4.7 MIME-Version