Developer adds HTTP/3 support to Kamal deploy tool via open-source fork and PR
A developer discovered that Kamal, a popular deployment tool using kamal-proxy, lacked the ability to enable HTTP/3 despite the proxy already supporting an --http3 flag. Two gaps prevented it from working: the flag was never passed to the proxy, and the required UDP port 443 for QUIC was never published alongside TCP. The developer forked Kamal and introduced a proxy.run.http3 option that addresses both issues in a single configuration line, with a guard preventing misconfiguration when ports are unpublished. The fix was deployed on watchbrandindex.com and verified successfully, with a pull request now submitted to the main Kamal repository for potential upstream inclusion. Separately, the developer also improved HTTP/3 discovery on a static S3 and CloudFront site by adding an HTTPS DNS resource record, allowing browsers to negotiate QUIC on the very first connection instead of upgrading only after an initial HTTP/2 handshake.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in