Hi Lukas, On Sat, Apr 15, 2023 at 02:08:03PM +0200, Lukas Tribus wrote: > Hi, > > On Sat, 15 Apr 2023 at 11:32, Willy Tarreau <[email protected]> wrote: > > Thus you're seeing me coming with my question: does anyone have any > > objection against turning "alpn h2,http/1.1" on by default for HTTP > > frontends, and "alpn h3" by default for QUIC frontends, and have a new > > "no-alpn" option to explicitly turn off ALPN negotiation on HTTP > > frontends e.g. for debugging ? > > For H2 I agree, and just to state which I think it's obvious: when > alpn is already configured the behaviour will remain as-is, the change > would only impact bind lines without alpn keyword.
Absolutely, that's how I'm seeing it. > For QUIC frontends, they are explicit anyway, so yes, I think "alpn > h3" should be implicit in HTTP mode, unless we expect to negotiate > different alpn protocols on top of QUIC (but I guess in this case the > frontend would be in TCP mode). Yes indeed, and I still have no idea how long it will take before we see new protocols being transported over QUIC in a mainstream way (but I don't want to go into any direction making this impossible of course). > > And if we change this default, do you prefer that we do it for 2.8 that > > will be an LTS release and most likely to be shipped with next year's > > LTS distros, or do you prefer that we skip this one and start with 2.9, > > hence postpone to LTS distros of 2026 ? > > I agree this should be in 2.8 LTS. OK, thank you very much! Willy
