backport rfc 9149 ticket_request extension to rel-0.23 - #3132
Merged
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## rel-0.23 #3132 +/- ##
=========================================
Coverage 95.31% 95.32%
=========================================
Files 97 97
Lines 21942 21979 +37
=========================================
+ Hits 20914 20951 +37
Misses 1028 1028 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
hz2
force-pushed
the
ft/rfc9149-backport
branch
2 times, most recently
from
July 9, 2026 18:51
bcea9f6 to
53cc395
Compare
Member
|
Can you rebase this on top of ? |
Add a `max_tls13_tickets` field to `ServerConfig` that caps the number of tickets the server will send in response to a client ticket_request extension. Defaults to 0 (disabled), preserving current behavior. This is the backwards-compatible equivalent of the `Tls13Tickets` struct on `main`.
Allow a TLS 1.3 client to request a specific number of session tickets via the ticket_request extension, and let the server honor that request up to its configured max_tls13_tickets. The client sends new_session_count/resumption_count in its ClientHello (configured via ClientConfig::send_ticket_request); the server replies with the expected count in EncryptedExtensions and sends min(requested, max_tls13_tickets) NewSessionTicket messages. Backport of the feature from main, adapted for the rel-0.23 API surface.
djc
approved these changes
Jul 10, 2026
Benchmark resultsInstruction countsSignificant differencesThere are no significant instruction count differences Other differencesClick to expand
Wall-timeSignificant differencesThere are no significant wall-time differences Other differencesClick to expand
Memory usageKey:
Significant differencesThere are no significant memory usage differences Additional informationCheckout details:
|
Merged
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.
summary
backport of #3126 (merged to main) adapted for the rel-0.23 API surface.
the main difference from the
mainimplementation: instead of replacingsend_tls13_tickets: usizewithTls13Tickets { default, max }(breaking),this adds a new
max_tls13_tickets: usizefield that defaults to 0 (disabled).when non-zero and a client sends the ticket_request extension, the server
sends
min(requested, max_tls13_tickets)tickets.no breaking changes to the public API.
what's here
ExtensionType::TicketRequest(0x003a)ClientTicketRequest/ServerTicketRequestHintwire format typesClientConfig::send_ticket_request: Option<TicketRequest>(client opt-in)ServerConfig::max_tls13_tickets: usize(server opt-in, 0 = disabled)