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

Can support custom httpproxy? #40

Open
DummyAppTest opened this issue Oct 14, 2024 · 2 comments
Open

Can support custom httpproxy? #40

DummyAppTest opened this issue Oct 14, 2024 · 2 comments
Labels
enhancement New feature or request

Comments

@DummyAppTest
Copy link

Can support custom httpproxy?

@jochenkirstaetter
Copy link
Contributor

jochenkirstaetter commented Oct 14, 2024

Hello @DummyAppTest

Thanks for the question. Not yet.
I'm using SocketsHttpHandler in .NET compared to the HttpClientHandler in .NET Framework.

I'll add this to the roadmap.

Cheers, JoKi

@jochenkirstaetter jochenkirstaetter added the enhancement New feature or request label Oct 14, 2024
@jochenkirstaetter
Copy link
Contributor

jochenkirstaetter commented Oct 14, 2024

Hello @DummyAppTest

After looking further into this. I found that the SocketsHttpHandler could use a proxy by default.
See here:
https://github.com/dotnet/runtime/blob/6221ddb3051463309801c9008f332b34361da798/src/libraries/Common/src/System/Net/Http/HttpHandlerDefaults.cs#L24

The current implementation of the SDK does not set any value, hence the default behaviour applies. You should be able to specify proxy settings using the default mechanism to read proxy information from the settings file.

Anyway, I'll keep this on my roadmap, and see how a Proxy property could be exposed publicly.

Cheers, JoKi

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants