Skip to content
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

We should build browser-specific System.Net.WebProxy instead where we could have simple implementation #43751

Closed
buyaa-n opened this issue Oct 23, 2020 · 6 comments · Fixed by #50368
Assignees
Labels
arch-wasm WebAssembly architecture area-System.Net
Milestone

Comments

@buyaa-n
Copy link
Contributor

buyaa-n commented Oct 23, 2020

System.Net.WebProxy accessing APIs unsupported on browser. We should build browser-specific System.Net.WebProxy instead where we could have a simple implementation

Originally posted by @marek-safar in #43363 (comment)

@Dotnet-GitSync-Bot
Copy link
Collaborator

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

@Dotnet-GitSync-Bot Dotnet-GitSync-Bot added the untriaged New issue has not been triaged by the area owner label Oct 23, 2020
@buyaa-n buyaa-n added arch-wasm WebAssembly architecture area-System.Net labels Oct 23, 2020
@ghost
Copy link

ghost commented Oct 23, 2020

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

@marek-safar marek-safar removed the untriaged New issue has not been triaged by the area owner label Oct 23, 2020
@marek-safar
Copy link
Contributor

/cc @lewing @kjpou1

@lewing
Copy link
Member

lewing commented Oct 24, 2020

@marek-safar what sort of behavior do you want here?

@marek-safar marek-safar added this to the 6.0.0 milestone Oct 24, 2020
@marek-safar
Copy link
Contributor

I was thinking that we should annotate not working APIs and fix IsLocal to be simple check only.

@lewing
Copy link
Member

lewing commented Nov 22, 2020

@tqiu8 take a look at this then we can discuss the timeline.

@ghost ghost added the in-pr There is an active PR which will close this issue when it is merged label Mar 29, 2021
@ghost ghost removed the in-pr There is an active PR which will close this issue when it is merged label Mar 30, 2021
@ghost ghost locked as resolved and limited conversation to collaborators Apr 29, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
arch-wasm WebAssembly architecture area-System.Net
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants