Login
You're viewing the functional.cafe public feed.
  • Nov 19, 2026, 3:02 PM

    @SecurityWriter unfortunately not many web frameworks support h2 or h2c (cleartext http2). Nginx didn't support h2 upstreams until version 1.29.4 (released December 2025, not in Debian stable yet).

    So in most cases you won't have end-to-end http2 and you'll end up accepting h2 only to transform it to http1, which is bad and has caused many security issues in itself. See http1mustdie.com for example.

    If you can't do end-to-end http2, I think end-to-end http1 is the best alternative.

    💬 1🔄 0⭐ 0

Replies

  • Nov 19, 2026, 5:28 PM

    @jomo I have seen this initiative. But given the problems with HTTP/2 in addition to compatibility, migrating to the worse alternative shouldn’t be the way forward.

    HTTP/3 and QUIC are arguably worse considering privacy and security.

    So for most people, mitigating HTTP issues is more palatable than upgrading.

    💬 0🔄 0⭐ 0