[FEAT] Out-of-the-box support for HTTP/2

[felipecrs]

Is this a new feature request?

• I have searched the existing issues

Wanted change

This issue is more like a question/suggestion/open discussion.

If you switched from NGINX to Caddy, you would have HTTP/2 and HTTP/3 QUIC for free.

Not to mention Caddy's automatic HTTPS certificates handling.

Reason for change

I wonder if that will improve performance even more.

Proposed code change

Installing Caddy is fairly simple, as it's a single executable.

If you think this idea is promising, I may help to experiment and even implement.

What do you think?

[github-actions]

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

[aptalca]

Nginx also supports http2 and quic. As an org, we don't recommend using individual certs in containers. We publish and support (and strongly recommend) an nginx based reverse proxy called SWAG, which makes it extremely easy to set up with auth and 2fa, and with built in proxy confs for most if not all the images we publish.

[felipecrs]

Great, I re-title this issue to remove mention of Caddy then.

[thelamer]

Can you explain how this would work please?
This is a websocket application not webtransport.

[felipecrs]

Yeah, we can agree HTTP/3 / QUIC / WebTransport is not something for now.

But WebSockets over HTTP/2 is a thing.

[ehfd]

If WebSockets over HTTP/2 is something we might really support, that does not mean that WebSockets through HTTP/1.1 Upgrade should be scrapped, due to environments requiring precisely HTTP/1.1 Upgrade.

[felipecrs]

For sure. I don't think support for HTTP/1.1 should be removed.

[LinuxServer-CI]

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.