doc: remove outdated TLS authorized docs warning - #65597
Merged
Merged
Conversation
Signed-off-by: Tim Perry <pimterry@gmail.com>
nodejs-github-bot
added
doc
lpinca
approved these changes
Aug 27, 2026
BethGriggs
approved these changes
Aug 28, 2026
pimterry
added
the
commit-queue
Collaborator
|
Landed in 104285a |
nodejs-github-bot
removed
the
commit-queue
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
4 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.
In #64584, we documented the long-term weird behaviour of
authorizedon resumed TLS 1.3 sessions, treating it as a caveat that users need to manually handle.The conclusion of #64677 was that this weird behaviour actually doesn't need to be accepted, and we can fix it as a non-breaking change, so this caveat no longer applies. This PR fixes that: keeping the explanatory paragraph but trimming it down to the new fixed reality.