Re: RFC 1522 (for HTTP 1.1 Warnings)

To: Klaus Weide <kweide@tezcat.com>
Subject: Re: RFC 1522 (for HTTP 1.1 Warnings)
From: "Martin J. Duerst" <mduerst@ifi.unizh.ch>
Date: Mon, 16 Dec 1996 20:05:59 +0100 (MET)
cc: www-international@w3.org
From www-international-request@www10.w3.org Mon Dec 16 14: 14:02 1996
In-Reply-To: <Pine.SUN.3.95.961216123445.25775A-100000@huitzilo.tezcat.com>
Message-ID: <Pine.SUN.3.95.961216200035.242M-100000@enoshima>
Sender: mduerst@enoshima
X-List-URL: http://www.w3.org/pub/WWW/Archives/Public/www-international

On Mon, 16 Dec 1996, Klaus Weide wrote:

> Another oddness of this RFC1522-encoding-in-HTTP-headers business is
> that it violates the rules for using this encoding in MIME.  RFC 2047,
> the new version of "MIME Part Three" which supersedes RFC1522, explicitly
> states:
> 
>    + An 'encoded-word' MUST NOT appear within a 'quoted-string'.
> 
> (And I understand this is not a new rule, it was already implicit
> in RFC 1522 syntax.)

Seems that there are more oddities comming to light every day.
Removing RFC1522 from HTTP headers may not be a bad idea then.

Anyway, based on the suggestion of several of you, I have moved
the discussion to http-wg (mail to http-wg@cuckoo.hpl.hp.com,
[un]subscription to http-wg-request@cuckoo.hpl.hp.com).

See you there.	Martin.

References:

Re: RFC 1522 (for HTTP 1.1 Warnings)

From: Klaus Weide <kweide@tezcat.com>

Prev: Re: Charset support (was: Accept-Charset support)i
Next: Re: RFC 1522 (for HTTP 1.1 Warnings)
Index: Message index of www-international@w3.org mailing list
Thread: Thread index of www-international@w3.org mailing list