3 ms·
No need. Just convince the king (e.g. Google for HTTP) to make a tweak in the next standard version.
by nsnshsuejeb 2y ago
No need. Just convince the king (e.g. Google for HTTP) to make a tweak in the next standard version.
- vitus 2y agoGood 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.