Feature Description
description - The built-in Cosmos reverse proxy currently handles HTTP/1.1 and HTTP/2 but does not support or advertise HTTP/3 (QUIC) connections.
Running heavy ServApps like Nextcloud behind Cosmos currently misses out on standard QUIC benefits, especially for mobile clients, including connection migration between wifi and cellular without dropping uploads, and faster parallel loading for assets like photo galleries over dodgy connections.
current behaviour and testing:
Router configured to forward both TCP and UDP 443 to the Cosmos host.
Tested via http3check.net and curl --http3.
Connection falls back to HTTP/2.
The server response is missing the Alt-Svc header required to advertise QUIC
HTTP/1.1 302 Found
Server: Apache/2.4.66 (Debian)
X-Served-By-Cosmos: 1
expected behaviour: The Cosmos proxy binds to UDP 443, accepts external QUIC connections, serves the Alt-Svc header, and proxies the traffic internally to ServApps via standard HTTP/TCP.
Feature Description
description - The built-in Cosmos reverse proxy currently handles HTTP/1.1 and HTTP/2 but does not support or advertise HTTP/3 (QUIC) connections.
Running heavy ServApps like Nextcloud behind Cosmos currently misses out on standard QUIC benefits, especially for mobile clients, including connection migration between wifi and cellular without dropping uploads, and faster parallel loading for assets like photo galleries over dodgy connections.
current behaviour and testing:
Router configured to forward both TCP and UDP 443 to the Cosmos host.
Tested via http3check.net and
curl --http3.Connection falls back to HTTP/2.
The server response is missing the Alt-Svc header required to advertise QUIC
expected behaviour: The Cosmos proxy binds to UDP 443, accepts external QUIC connections, serves the Alt-Svc header, and proxies the traffic internally to ServApps via standard HTTP/TCP.