Skip to content
Better HN
Top
New
Best
Ask
Show
Jobs
Search
⌘K
undefined | Better HN
0 points
Ekaros
1y ago
0 comments
Share
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.
0 comments
default
newest
oldest
nsnshsuejeb
1y ago
No need. Just convince the king (e.g. Google for HTTP) to make a tweak in the next standard version.
vitus
1y ago
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.
j
/
k
navigate · click thread line to collapse