Hacker News Reader

Comment by francislavoie | Hacker News Reader

Just a reminder, Caddy supports and enables HTTP/3 by default as of v2.6.0 (from ~September).

It's strange that I had to set up Caddy as a proxy just to connect to a nodejs http server, because setting up Caddy was so much easier than setting up https in nodejs.

But at least it just works for everything I have thrown to it.

That's because node and friends are commonly deployed with tls termination at a load balancer level, and that you likely want a faster server serving up static content (Apache/nginx/caddy/whatever). Given the choice between encouraging people to shoddily wire up TLS in their apps, and providing plug and play support in things like Caddy, I prefer the latter any day of the week!

I don't understand what ,,shoddily wire up'' means. I had to create, maintain and monitor a new service that just to add encryption to my simple web server (actually just to be able to connect to my web server from my browser), that should just be a simple function call.

If everything would be implemented like this, next time leftpad should be a web service on my machine as well?

Ah yes, that update broke one of our applications. I've been meaning to try the update again with HTTP3 disabled but haven't had the time.

If something broke, then please open an issue on GitHub or ask for help on the Caddy community forums.

To be clear, I doubt it was a bug in Caddy. Probably a misconfigured firewall at some point, or a bug with the outdated version of video.js or something.

Basically all I know is:

- Updated from Caddy 2.5.1 to 2.6.2.

- Customer reported video was buffering endlessly.

- Downgraded Caddy to 2.5.1.

- Issue resolved.

But I can file an issue like that if you think it would be helpful.

If it can be reproduced, that'd be helpful. We'd need to know what the client was, what the requests were like, etc. Caddy 2.6 works great with videos from our own testing and production experience.

I've observed worse performance with caddy+http3 so I disabled it. That was especially noticable on larger files

Try the latest release. Correct implementation was priority 1, then optimization was recently performed by the authors of quic-go. Still more optimizing under way.

Sweet, my decision to switch from nginx to Caddy continues to be a great one.

Reply on news.ycombinator.com