CGI.pm programmed with RFC 822 standards WTF!

$h4X4_|=73}{ has asked for the wisdom of the Perl Monks concerning the following question:

I tool a look into CGI.pm version on cpan and github. They both have a code comment that refers a fix per RFC 822 standards.
RFC 822 is for email protocol, so why the hell is there even a reference to it in a HTTP protocol?

Update: Fix spelling

Comment on CGI.pm programmed with RFC 822 standards WTF!

Replies are listed 'Best First'.
Re: CGI.pm programmed with RFC 822 standards WTF! by Corion (Patriarch) on Aug 16, 2016 at 08:06 UTC
It may surprise you, but the HTTP headers, at least up until very recent RFCs that superceded RFC 2616, allowed split headers, and that split was according to 822. Often, it helps to look at the source material for a protocol instead of only reading the implementation(s). Searching the (linked) RFC 2616 returns many more instances where HTTP relies on pre-existing standards like 822.	[reply]
A reply falls below the community's threshold of quality. You may see it by logging in.