Opt KAS requests into HTTP/3#42
Merged
Merged
Conversation
Set assumesHTTP3Capable on all three KASRewrapClient request sites (rewrapNanoTDF, rewrapTDF, public-key fetch). The KAS advertises alt-svc: h3=":443", so this negotiates HTTP/3 on the first hop instead of starting on HTTP/2; URLSession falls back to HTTP/2 for non-h3 servers. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Summary
Opt KAS requests into HTTP/3 on the first hop.
assumesHTTP3Capableis set on all threeKASRewrapClientrequest sites —rewrapNanoTDF,rewrapTDF, and the KAS public-key fetch. The KAS endpoints (platform.arkavo.net,kas.arkavo.net) advertisealt-svc: h3=":443", but a normal request starts on HTTP/2 and only upgrades a later connection. This flag lets the very first request negotiate HTTP/3; URLSession falls back to HTTP/2 automatically when a server is not h3-capable.Note:
assumesHTTP3Capableis a property onURLRequest(macOS 11.3+), notURLSessionConfiguration.Testing
swift build✅swift test --filter KASRewrapClient→ 21/21 passed ✅platform.arkavo.net:URLSessionTaskMetrics.networkProtocolName == "h3"with the flag set (h2without).🤖 Generated with Claude Code