Assertion | Section | Test | Quote/Description |
---|---|---|---|
rfc2557-1 | 4.4.1 Encoding of URIs containing inappropriate characters | rfc2557-BF-01.htm |
[if a URI contains characters that are inappropriate for an RFC 822 header,]
all spaces and other illegal characters in it must be encoded using one
of the methods described in
[MIME3] section 4.
[The encoded word must be preceded with "=?UTF-8?Q?" and ended with "?="
"=?UTF-8?Q?dir=2FThisExample=2Ejpg?=" ] |
rfc2557-2 | 4.4.1 Encoding of URIs containing inappropriate characters | rfc2557-BF-01.mx | This encoding MUST only be done in the header, not in the HTML text. |
rfc2557-3 | 4.4.1 Encoding of URIs containing inappropriate characters | rfc2557-BF-01.mx | Receiving clients MUST decode the [MIME3] encoding in the heading before comparing URIs in body text to URIs in Content-Location headers. |
rfc2557-4 | 4.4.2 Folding of long URIs | rfc2557-BF-01.mx | Encoding as discussed in clause 4.4.1 MUST be done before such folding. |
rfc2557-5 | 4.4.2 Folding of long URIs | rfc2557-BF-01.mx |
... Folding ... using the algorithm defined in [RFC2017] section 3.1. [
|
rfc2557-6 | 5. Base URIs for resolution of relative URIs | rfc2557-BF-02.mx | When the methods above do not yield an absolute URI, a base URL of "thismessage:/" MUST be employed. |