LISTSERV mailing list manager LISTSERV 15.5

Help for MHTML Archives

MHTML Archives

MHTML Archives


Next Message | Previous Message
Next in Topic | Previous in Topic
Next by Same Author | Previous by Same Author
Chronologically | Most Recent First
Proportional Font | Monospaced Font


Join or Leave MHTML
Reply | Post New Message
Search Archives

Subject: Re: More on wrongly(?) formatted urls
From: Jacob Palme <[log in to unmask]>
Reply-To:IETF working group on HTML in e-mail <[log in to unmask]>
Date:Wed, 20 Aug 1997 19:47:36 +0200

text/plain (49 lines)

Here is a new draft text. It is based on the text proposed
by Larry M and also tries to take into account the comments
by Martin J D.

Some changes in other places of RFC 2110 may also be
necessary, I will check this when I update the draft.

     Handling of URLs containing inappropriate characters

     Some URLs may contain characters that are inappropriate
     for an RFC 822 header, either because the URL itself
     has an incorrect syntax or the URL syntax has changed to
     allow characters not allowed in mail headers. To include
     such a URL in a mail header, an implementation can either
     (a) arrange so that the URL becomes correctly formatted or
     (b) encode the header using the encoding method described
     in RFC 2047.

     Method (a) MUST be applied to the URL both in Content-
     Location headers and in body text. It MUST NOT be reversed
     by receiving mailers before matching hyperlinks to body

     Method (b) can be applied only to the URL in Content-
     Location headers and MUST be reversed by receiving clients
     before comparing hyperlinks in body text to URLs in
     Content-Location headers.

     Method (a) is not always easy. It may include cooperation
     with the user and the software which produced the faulty
     URL. The encoding method of RFC 1738 can make a correct
     URL faulty if not done the right way. Changing the URL of
     documents already available on the Internet or an Intranet
     may invalidate existing links to this document. Changing
     the HTML body may invalidate message integrity checks.

     If method (b) is used, the charset US-ASCII can be used,
     or, if the URL contains octets outside of the 7-bit range,
     "UKNOWN-8BIT" [RFC 1428] or "UTF8" may be appropriate.
     Note that for MHTML processing (matching of URLs in body
     text to URL in Content-Location headers) the choice of
     character need not be the "correct" set, it need only
     be a set which, after reversal of the encoding by the
     receiving mailer, returns the same octet string as before
     the encoding.

Jacob Palme <[log in to unmask]> (Stockholm University and KTH)
for more info see URL:

Back to: Top of Message | Previous Page | Main MHTML Page



CataList Email List Search Powered by the LISTSERV Email List Manager