LISTSERV mailing list manager LISTSERV 15.5

Help for MHTML Archives


MHTML Archives

MHTML Archives


View:

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

Options:

Join or Leave MHTML
Reply | Post New Message
Search Archives


Subject: Re: More on wrongly(?) formatted urls
From: Nick Shelness <[log in to unmask]>
Reply-To:IETF working group on HTML in e-mail <[log in to unmask]>
Date:Tue, 26 Aug 1997 15:28:23 +0100
Content-Type:text/plain
Parts/Attachments:
Parts/Attachments

text/plain (19 lines)


Jacob, You write (> ) in response to my earlier note (>> ):-

>> RFC 1738 describes how to encode URLs. Clearly, if we only encounter
URLs
>> in text/html objects that are RFC 1738 compliant we have no problem as
they
>> will also be RFC 822 header syntax compliant. The problem arises when we
>> encounter URLs that are not RFC 1738 compliant and which, therefore, may
>> not be RFC 822 header syntax compliant. This then is the case, and the
only
>> case, in which 2047 encoding is required.
>That is a little vague to write in a standard. I would prefer to say that
>all URLs which are not RFC 1738 compliant MUST be encoded with RFC 2047
>encoding. That is, that we should not specify our own definition of which
>character codes need and need not 2047 encoding.

I agree completely with your suggestion.

Nick

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

Permalink



LISTSRV.NORDU.NET

CataList Email List Search Powered by the LISTSERV Email List Manager