W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2009

Re: header parsing, trailing OWS

From: Julian Reschke <julian.reschke@gmx.de>
Date: Wed, 07 Oct 2009 17:15:48 +0200
Message-ID: <4ACCB0A4.5000400@gmx.de>
To: David Morris <dwm@xpasc.com>
CC: ietf-http-wg@w3.org
David Morris wrote:
> 
> 
> On Thu, 24 Sep 2009, Julian Reschke wrote:
> 
>> Hi,
>>
>> In the current edits, the last 'MAY' is a 'SHOULD', which makes it read
>>
>> "A field value MAY be preceded by optional whitespace (OWS); a single 
>> SP is preferred. The field value does not include any leading or 
>> trailing white space: OWS occurring before the first non-whitespace 
>> character of the field value or after the last non-whitespace 
>> character of the field value is ignored and SHOULD be removed without 
>> changing the meaning of the header field."
> 
> 
> Doesn't read smoothly .... and infact turns into a directive rather than 
> a permission.
> 
> One alternate to illustrate my point ...
>    "SHOULD be removed" --> "SHOULD be able to"
> another ... replace the remainder after "the field value is ignored and"
> with:
>     "removing OWS before or after the field value SHOULD NOT change the
>      meaning of the header field."

I think we should just say:

"OWS occurring before the first non-whitespace character of the field 
value or after the last non-whitespace character of the field value is 
ignored and can be removed without changing the meaning of the header 
field."

...replacing the MAY in draft 07, and the SHOULD in the current edits, 
by "can". RFC2119 terminology is not needed here.

BR, Julian
Received on Wednesday, 7 October 2009 15:16:28 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:51:12 GMT