Alan Gutierrez wrote: > > This just in from RFC 2068 HTTP/1.1 - 4.2 Message Headers: > > The field value may be preceded by any amount of LWS, though a single SP > is preferred. Header fields can be extended over multiple lines by > preceding each extra line with at least one SP or HT. Yes, similar requirements are in RFC 822, which talks about SMTP headers. The header and unheader function would be able to support them. Let's take up further concerns by addressing the Text::Header module itself; I'll check out your other emails and see what can be integrated. Feel free to email me offline as well. Thanks, Nate
- RFC 333 (v1) Add C<header> and C<unheader>... Perl6 RFC Librarian
- Re: RFC 333 (v1) Add C<header> and C<unh... John Barnette
- Re: RFC 333 (v1) Add C<header> and C<... Jonathan Scott Duff
- Re: RFC 333 (v1) Add C<header> and ... Nathan Wiger
- Re: RFC 333 (v1) Add C<header> and C<unh... Philip Newton
- Re: RFC 333 (v1) Add C<header> and C<... Nathan Wiger
- Re: RFC 333 (v1) Add C<header> and ... Philip Newton
- Re: RFC 333 (v1) Add C<header> and C<unh... Alan Gutierrez
- Re: RFC 333 (v1) Add C<header> and C<unh... Alan Gutierrez
- Re: RFC 333 (v1) Add C<header> and C<unh... Alan Gutierrez
- Re: RFC 333 (v1) Add C<header> and C<... Nathan Wiger
- Re: RFC 333 (v1) Add C<header> and C<unh... Jerrad Pierce
- Re: RFC 333 (v1) Add C<header> and C<... Nathan Wiger