Re:Pre-auth RCE in Nginx HTTP/2 handling
by gkbrk on Wednesday November 18, 2026 @01:08PM
(#50549820)
Because any HTTP spec after 1.1 is incredibly complicated. You can implement HTTP/1 in half a day, and HTTP/1.1 in a day. But HTTP/2 will probably take you a month and HTTP/3 might take something like 6 months.
[ Parent
| on HN ]
Re:Pre-auth RCE in Nginx HTTP/2 handling
by qweqwe14 on Wednesday November 18, 2026 @01:47PM
(#50550386)
Do you realize that no one writes toy HTTP implementations from scratch? I get that you might have a "suckless" mindset but that's just not how the real world works.
Re:Pre-auth RCE in Nginx HTTP/2 handling
by dannyw on Wednesday November 18, 2026 @02:38PM
(#50551033)
A simpler protocol has less surface area for vulnerabilities. I think GP was just using that as an expression of this.
Re:Pre-auth RCE in Nginx HTTP/2 handling
by doodlesdev on Wednesday November 18, 2026 @02:38PM
(#50551037)
[delayed]
Re:Pre-auth RCE in Nginx HTTP/2 handling
by cozzyd on Wednesday November 18, 2026 @10:13PM
(#50555591)
I've definitely done that before on a microcontroller.
Re:Pre-auth RCE in Nginx HTTP/2 handling
by postalrat on Wednesday November 18, 2026 @02:17PM
(#50550729)
You forgot about all the networking hardware and software those run on. The difference is negligible.
Re:Pre-auth RCE in Nginx HTTP/2 handling
by Liuser on Wednesday November 18, 2026 @02:43PM
(#50551106)
It boggles my mind that people are patting themselves on the back for staying on old tech stacks and using a discovered vulnerability as further justification of their decision to stay on h1.1.
No one is implementing h2 and h3 from the ground up.
Vulnerabilities are discovered all the time, the solution is to patch, and if you can’t, downgrade to h1.1 as a mitigation.
But there are many legitimate use cases for h2 (eg bidi streaming, latency improvements) and h3 (eg seamless network switching). If you don’t need these features that’s also fine.