-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Replace TlsStream type by using SslStream directly #106451
Conversation
Tagging subscribers to this area: @dotnet/ncl, @bartonjs, @vcsjones |
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.
Good riddance, thank you
…eam.cs Co-authored-by: Miha Zupan <mihazupan.zupan1@gmail.com>
src/libraries/System.Net.Requests/src/System/Net/FtpDataStream.cs
Outdated
Show resolved
Hide resolved
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.
LGTM. Hopefully we will have whole release to bake it.
Follow up after #106362.
The
TlsStream
type does not bring much useful behavior on top of plainSslStream
, removing the type prevents issues like #99276 stemming from missing delegating overloads from resurfacing in the future.Summary of changes:
There was some extra plumbing necessary in case of System.Net.Requests where the code needs to manipulate the underlying NetworkStream (mainly accessing the Socket directly), so the original
NetworkStream
is being passed along as well where appropriate.