| Assertion | Section | Quote/Description |
|---|
| rfc2557-1 | 4.4.1 Encoding of URIs containing inappropriate
characters |
[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.
|
| rfc2557-2 | 4.4.1 Encoding of URIs containing inappropriate characters |
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 |
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 |
Encoding as discussed in clause 4.4.1 MUST be done before such folding.
|
| rfc2557-5 | 4.4.2 Folding of long URIs |
... Folding ... using the algorithm defined in [RFC2017] section 3.1.
|
