-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
[release/7.0-staging] [maccatalyst] Make sure MacProxy is included in System.Net.Http #91817
[release/7.0-staging] [maccatalyst] Make sure MacProxy is included in System.Net.Http #91817
Conversation
… System.Net.Http Backport of dotnet#91473 to release/7.0
Tagging subscribers to this area: @dotnet/ncl Issue DetailsBackport of #91473 to release/7.0
|
Approved by tactics over email |
/azp run runtime-extra-platforms |
Azure Pipelines successfully started running 1 pipeline(s). |
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.
Signing off on behalf of @steveisok who confirmed the CI looks good.
Backport of #91473 to release/7.0
Fixes #90258
/cc @steveisok
Customer Impact
A customer reported #90258 where they were using
ClientWebSocket.ConnectAsync
in their MAUI app behind a proxy server and ran into connection issues using MacCatalyst. This is due to an incorrect condition inSystem.Net.Http.csproj
that does not include the relevant source code.Testing
Manually validated connection with a proxy works
Risk
Low
IMPORTANT: If this backport is for a servicing release, please verify that:
The PR target branch is
release/X.0-staging
, notrelease/X.0
.If the change touches code that ships in a NuGet package, you have added the necessary package authoring and gotten it explicitly reviewed.