This repository has been archived by the owner on Jan 23, 2023. It is now read-only.
[2.1] Add server-side SNI support #28646
Closed
Conversation
This file contains 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
|
Is this necessary if we're going to be doing a merge from master to 2.1 today or over the weekend anyway? These one-off ports can make that more difficult. cc: @weshaggard |
|
@stephentoub I didn't realize there will be port happening, I thought it was already locked. If we are in fact doing it we can close this PR |
|
The only reason would be to deliver the bits to ASP.NET faster - @Tratcher would it help you? If not, let's not complicate things ... |
|
I'm going to close this PR in this case |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
2.1 squashed port of #28278
Seems like CI is hanging on master but we can still send a port PR
cc: @karelz @Tratcher