Re:CRLF is obsolete and should be abolished
by bigstrat2003 on Sunday October 13, 2024 @05:07PM
(#41831592)
Yeah, I have no idea what the author is smoking. Deliberately breaking standards is simply not an acceptable solution to the problem, even if it were a serious problem (it's not).
[ Parent
| on HN ]
Re:CRLF is obsolete and should be abolished
by Ekaros on Sunday October 13, 2024 @05:09PM
(#41831612)
If there truly is a problem with existing protocols, propose and properly design new one that can replace it. Then if it is technically superior solution it should win in long run.
Re:CRLF is obsolete and should be abolished
by nsnshsuejeb on Sunday October 13, 2024 @05:51PM
(#41831994)
No need. Just convince the king (e.g. Google for HTTP) to make a tweak in the next standard version.
Re:CRLF is obsolete and should be abolished
by vitus on Monday October 14, 2024 @07:55AM
(#41836672)
Good news! Both HTTP/2 and HTTP/3 use a packed binary representation for headers, so CRLF is nowhere to be found in RFC 9113 / 9114.
I don't see value in picking on Google or HTTP here, even if it is fashionable to do so.