1 - 2 - 7 - 8 - A - B - C - D - E - F - G - H - I - J - L - M - N - O - P - Q - R - S - T - U - V - W - X
message header
Click on the red underlined text to get to the source
... Content-Transfer-Encoding header field appears as part of a
message header, it applies to the entire body of that message. If a
Content-Transfer-Encoding header field ...
... header field. However, in no event are
headers (either message headers or body-part headers) allowed to
contain anything other than ASCII characters ...
... apply to the subtypes "message/partial" and "message/external-body",
as specified below. The message header fields are always US-ASCII in
any case, and data within the body can still be encoded, in which
...
... message/external-body", it consists of a
header, two consecutive CRLFs, and the message header for the
encapsulated message. If another pair of consecutive CRLFs appears,
...
... encapsulated message. If another pair of consecutive CRLFs appears,
this of course ends the message header for the encapsulated message.
However, since the encapsulated ...
... parameter.
The embedded message header fields which appear in the body of the
message/external-body data must be used to declare the Content-type ...
... header field. However, in no event are
headers (either message headers or body-part headers) allowed to
contain anything other than ASCII characters ...