From: Paul Overell (paulo@turnpike.com)
Date: Tue Feb 26 2002 - 04:10:38 CST
In message <Gry55n.DLD@clw.cs.man.ac.uk>, Charles Lindsey
<chl@clw.cs.man.ac.uk> writes
>In <3xIcKzJT34Z8QA9I@pillar.turnpike.com> Paul Overell
><paulo@turnpike.com> writes:
>
>>Since all {USENET}-content starts with [CFWS], and we only require a
>>single space after the colon, this should be
>
>
>> {USENET}-header =3D {USENET}-name ":" SP {USENET}-content
>> *( [CFWS] ";" ( {USENET}-parameter /
>> other-parameter ) )
>
>>(This just removes a trivial parsing ambiguity, it is not a material
>>change to the syntax).
>
>Well that looked simple enough, but on inspection I found that some
>contents did not start with CFWS :-( .
>
>So there followed a long trawl to fix that bug in umpteen places. I have
>now established the following invariant:
>
> NOTE: It may be observed that every {USENET]-content begins and
> ends with an optional CFWS (or FWS in the case of the
> Newsgroups-, Distribution-, Path- and Followup-To-headers
also Date and Expires
>).
> Moreover, every {USENET}- or other-parameter also begins and
> ends with an optional CFWS.
>
>The complete Collected Syntax as fixed is reproduced below. Will Paul
>Overell please check is carefully to see that this problem is truly fixed?
>
OK, I've checked that every -content and -parameter begins and ends with
[CFWS] or [FWS].
Also, a stray "
> posting-account-parameter
> = [CFWS] Posting-Account-token" [CFWS] "=" value
should be
posting-account-parameter
= [CFWS] Posting-Account-token [CFWS] "=" value
Regards
-- Paul Overell T U R N P I K E