Uh oh!
There was an error while loading. Please reload this page.
[iOS] [Android] Remove PNSE from some HttpClientHandler methods - #57555
Conversation
Since HttpClientHandler on mobile can support both the underlying native handler and SocketsHttpHandler, it doesn't make sense to always throw PNSE on some methods due to only the native handler not supporting them. Fixesdotnet#55986
ghost
commented
Aug 17, 2021
Note regarding the This serves as a reminder for when your PR is modifying a ref *.cs file and adding/modifying public APIs, to please make sure the API implementation in the src *.cs file is documented with triple slash comments, so the PR reviewers can sign off that change. |
ghost
commented
Aug 17, 2021
Tagging subscribers to this area: @dotnet/ncl Issue DetailsSince HttpClientHandler on mobile can support both the underlying native handler and SocketsHttpHandler, it doesn't make sense to always throw PNSE on some methods due to only the native handler not supporting them. Fixes #55986
|
marek-safar
commented
Aug 27, 2021
@akoeplinger was this fix backported? |
steveisok
commented
Aug 27, 2021
@marek-safar It got in before the snap. |
Since HttpClientHandler on mobile can support both the underlying native handler and SocketsHttpHandler, it doesn't make sense to always throw PNSE on some methods due to only the native handler not supporting them.
Fixes#55986