W3C home > Mailing lists > Public > ietf-http-wg-old@w3.org > May to August 1996

MIME and Warning header syntax

From: Klaus Weide <kweide@tezcat.com>
Date: Wed, 3 Jul 1996 09:01:52 -0500 (CDT)
To: http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
Message-Id: <Pine.SUN.3.94.960703083614.786B-100000@xochi.tezcat.com>
The syntax for the Warning response-header, in the case of a character
set different from ISO-8859-1, conflicts with RFC 1522 as clarified 
by draft-ietf-822ext-mime-hdrs-00.txt.  If HTTP/1.1 is meant to allow
encoded-words in a quoted-string, this should be clearly identified
as a deviation from the rules in RFC 1522 and its successor.

<URL:ftp://ietf.cnri.reston.va.us/internet-drafts/
draft-ietf-http-v11-spec-05.txt>:

> 14.45 Warning
> ...
> 
> Warning headers are sent with responses using:
> 
>        Warning    = "Warning" ":" 1#warning-value
> 
>        warning-value = warn-code SP warn-agent SP warn-text
>...
>        warn-text  = quoted-string
>... 
> If a character set other than ISO-8599-1 is used, it MUST be encoded in
> the warn-text using the method described in RFC 1522 [14].
  
<URL:ftp://ietf.cnri.reston.va.us/internet-drafts/
draft-ietf-822ext-mime-hdrs-00.txt>:

> 5. Use of encoded-words in message headers
> ...
> 
>    These are the ONLY locations where an 'encoded-word' may appear.  In
>    particular:
>... 
> 
>    + An 'encoded-word' MUST NOT appear within a 'quoted-string'.
>... 
-- 
Klaus Weide <kweide@tezcat.com>
Received on Wednesday, 3 July 1996 07:07:41 EDT

This archive was generated by hypermail pre-2.1.9 : Wednesday, 24 September 2003 06:32:04 EDT