-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add StreamConformanceTest for HTTP CONNECT stream #50699
Conversation
Tagging subscribers to this area: @dotnet/ncl Issue Details@stephentoub @dotnet/ncl
|
/azp run runtime-libraries-coreclr outerloop |
Azure Pipelines successfully started running 1 pipeline(s). |
Assert.True(pair.Stream2.CanRead); | ||
return pair; | ||
} | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this testing a different stream than Http1UpgradeResponseStreamConformanceTests is testing?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's the same stream, but a different way of constructing it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From a "we know the implementation" perspective, this doesn't seem like it's actually testing anything further:
else if (ReferenceEquals(normalizedMethod, HttpMethod.Connect) && response.StatusCode == HttpStatusCode.OK)
{
responseStream = new RawConnectionStream(this);
_connectionClose = true;
}
else if (response.StatusCode == HttpStatusCode.SwitchingProtocols)
{
responseStream = new RawConnectionStream(this);
}
but if you really think it's worth adding additional stream tests for, ok.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I think you're right here. I'll just close this.
@stephentoub @dotnet/ncl