Re: Headers folding

In <FC4B9A21400949B4A1D2EA4462B1FDAB@Iulius> =?iso-8859-15?Q?Julien_=C9LIE?= <[email protected]> writes:

>A.1.  Header Folding

>   NNTP allows a header line to be folded (by inserting a CRLF pair)
>   before any space or TAB character.

>   Both email and Netnews articles are required to have at least one
>   octet other than space or TAB on each header line.  Thus, folding can
>   only happen at one point in each sequence of consecutive spaces or
>   TABs.  Netnews articles are further required to have the header name,
>   colon, and following space all on the first line; folding may only
>   happen beyond that space.  Finally, some non-conforming software will
>   remove trailing spaces and TABs from a line.  Therefore, it might be
>   inadvisable to fold a header after a space or TAB.

>   For maximum safety, header lines SHOULD conform to the following
>   syntax rather than to that in Section 9.7.


>     header = header-name ":" SP [header-content] CRLF
>     header-content = [WS] token *( [CRLF] WS token )

I think that comes to the same thing as USEFOR (except it is less
restrictive as regards the quoted-strings and whatnot).



>Well, my question is for 9.7:

>    header = header-name ":" [CRLF] SP header-content CRLF

>Is it a valid header for USEFOR?  and for RFC 5322?

I think it is valid in RFC 5322, but NOT in RFC 3977 and NOT in USEFOR.

>In A.1, it looks strange to have written the syntax this way:

>     header-content = [WS] token *( [CRLF] WS token )

>Hopefully it works!  (token does not contain WS but it comes
>afterwards with "WS token"!)

I think that is just to allow extra WS once you have got past the
obligatory first SP. I think it works.

-- 
Charles H. Lindsey ---------At Home, doing my own thing------------------------
Tel: +44 161 436 6131            Web: http://www.cs.man.ac.uk/~chl
Email: [email protected]      Snail: 5 Clerewood Ave, CHEADLE, SK8 3JU, U.K.
PGP: 2C15F1A9      Fingerprint: 73 6D C2 51 93 A0 01 E7 65 E8 64 7E 14 A4 AB A5