Caddyhttp: Enable HTTP/3 by Default

Re:Caddyhttp: Enable HTTP/3 by Default by mholt on Thursday September 08, 2022 @05:16PM (#32772193)

Marten is in the process of making a bunch of optimizations [0], as are we within Caddy, and 2.6 includes some of those. It will only get better with time.

Most users do not operate at nearly the volume required to feel the impact, including enterprises.

Would be interested in repeating your experiments and knowing your real world use case and seeing how similar they are.

[0]: https://github.com/lucas-clemente/quic-go/issues/3526

[ Parent | on HN ]

Re:Caddyhttp: Enable HTTP/3 by Default by kgersen on Thursday September 08, 2022 @05:32PM (#32772369)

We do speed tests hence we saw the issue. See https://github.com/golang/go/issues/47840

Yeah I agree this is a edge case, 99,99% of Caddy users don't push so much data ;)

But Caddy can't be used as a big files download server for instance, unless sticking with HTTP/1.1 (that and sendfile + kTLS not been supported last time I checked?) (at least with a single http instance).

Another issue for HTTP/3 is https://github.com/lucas-clemente/quic-go/wiki/UDP-Receive-B... Current Linux in WSL for instance has this issue. This will probably resolves over time as more and more Linux distros will take HTTP/3 requirements into account.

[ Parent | on HN ]

Re:Caddyhttp: Enable HTTP/3 by Default by mholt on Thursday September 08, 2022 @09:39PM (#32774305)

Caddy 2.6 has some optimizations for serving large files, including sendfile, but other optimizations too. No ktls yet, but maybe someday. It's just... kinda gnarly.

[ Parent | on HN ]

Re:Caddyhttp: Enable HTTP/3 by Default by kgersen on Friday September 09, 2022 @11:05AM (#32780118)

thx i'll look at v2.6.

[ Parent | on HN ]