Add support for serving HTTP/3#101
Merged
Merged
Conversation
aryan-25
added
🆕 semver/minor
FranzBusch
approved these changes
Jul 21, 2026
Comment on lines
+61
to
+62
| remoteAddress: nil, | ||
| localAddress: nil, |
Collaborator
Author
There was a problem hiding this comment.
HTTP3ServerConnectionMultiplexer vends out a HTTP3ServerConnection for each connection.
The problem is that the underlying connection channel cannot be accessed from HTTP3ServerConnection in its current shape.
I've set these properties to nil until we make some changes in HTTP3ServerConnection.
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
2 participants
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.
Motivation
Following from #98, this PR introduces support for serving HTTP/3.
Modifications
NIOHTTPServer+HTTP3.swiftwhich contains helper methods for setting up a QUIC channel, adding HTTP/3 handlers, and serving HTTP/3 connections.makeServerChannels().supportedHTTPVersions, only a QUIC channel is bound to the specified port. WhensupportedHTTPVersionsincludes HTTP/1.1 and/or HTTP/2 alongside HTTP/3, the QUIC UDP channel is bound on the same port as the TCP channel serving HTTP/1.1 and/or HTTP/2.Result
NIOHTTPServercan now serve HTTP/3.