I dont know, arguing that http/2 is safer overall is a... bold claim. It is sufficiently complex that there is no standard implementation in the Python standard library, and even third party library support is all over the place. requests doesn't support it; httpx has experimental, partial, pre-1.0 support. Python http/2 servers are virtually unavailable at all. And it's not just Python - I remember battling memory leaks, catastrophic deadlocks, and more in the grpc-go implementation of http/2, in its early days.HTTP 1.1 connection reuse is indeed more subtle than it first appears. But http/2 is so hard to get right.
Bender|6 months ago
The underlying vulnerability, tracked as CVE-2025-8671, has been found to impact projects and organizations such as AMPHP, Apache Tomcat, the Eclipse Foundation, F5, Fastly, gRPC, Mozilla, Netty, Suse Linux, Varnish Software, Wind River, and Zephyr Project. Firefox is not affected.
[1] - https://www.securityweek.com/madeyoureset-http2-vulnerabilit...
yencabulator|6 months ago
ameliaquining|6 months ago
jcdentonn|6 months ago
cyberax|6 months ago
Perhaps something like "HTTP/2-Lite" profile is in order? A minimal profile with just 1 connection, no compression, and so on.
spenczar5|6 months ago
I would endorse your idea, though, speaking more broadly! That does sound useful.
jiehong|6 months ago
Perhaps it isn’t that easy, but it could be put in common and used a bit everywhere.