Repository navigation
fix(caddy): advertise HTTP/3 on forwarded port - #10
Merged
Merged
Conversation
Adiker
force-pushed
the
docs/http3-service-configuration
branch
from
October 27, 2026 23:28
c0ba5fb to
1f583ef
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Document the HTTP/3 alternative port and update the deployable Muse Caddy snippet to advertise it on normal and error responses.
HTTP/3 was confirmed from a cellular network; HTTPS over TCP remains available.
Validation:
caddy validate --config ops/muse-status/Caddyfile, Muse probe unit tests,git diff --check, and repeated HTTP/2 and HTTP/3 health requests.Risk/rollback: If HTTP/3 becomes unavailable, send
Alt-Svc: clearfor all five service domains, including error responses, and verify HTTP/2. Clients with a stale cached alternative may need their browser network cache cleared.