Skip to content

Limit unique SNI to 63 chars in tests#47854

Merged
geoffkizer merged 2 commits intodotnet:masterfrom
aik-jahoda:jajahoda/snitest2
Feb 5, 2021
Merged

Limit unique SNI to 63 chars in tests#47854
geoffkizer merged 2 commits intodotnet:masterfrom
aik-jahoda:jajahoda/snitest2

Conversation

@aik-jahoda
Copy link
Contributor

The test generates SNI based on test name and argument to make it unique. However the SNI shouldn't be longer than 63 chars.
The PR also add another place when unique SNI is required for fix TLS1.3 test

Fixes #47378

@ghost
Copy link

ghost commented Feb 4, 2021

Tagging subscribers to this area: @dotnet/ncl
See info in area-owners.md if you want to be subscribed.

Issue Details

The test generates SNI based on test name and argument to make it unique. However the SNI shouldn't be longer than 63 chars.
The PR also add another place when unique SNI is required for fix TLS1.3 test

Fixes #47378

Author: aik-jahoda
Assignees: -
Labels:

area-System.Net.Security

Milestone: -

Copy link
Member

@wfurt wfurt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.
Does the limitation comes from length of single DNS label? (I would expect SNI to be longer since that can be FQDN)
How did the old code manifest the problem?

@geoffkizer
Copy link
Contributor

My understanding is that there's a limit of 255 on the whole host name, and also a limit of 63 on each part of the name.

@geoffkizer geoffkizer merged commit 5077dd4 into dotnet:master Feb 5, 2021
@ghost ghost locked as resolved and limited conversation to collaborators Mar 7, 2021
@karelz karelz added this to the 6.0.0 milestone May 20, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Some HTTP & TLS test are failing on Insider Preview Windows build

4 participants