-
Notifications
You must be signed in to change notification settings - Fork 67
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
Support passing default credentials to a proxy #305
Comments
Sorry it's taken us a while to get back to you. Default proxy support should already be in the tool. Under the hood, we're using |
@mungojam Just following up here. I still need to get this added to the documentation. But do you have any additional details on what issues you ran into? |
Hiya, sorry haven't got around to looking into it again. I think the issue is more if you have a Windows authenticated proxy. .net core requires a one-liner to tell it to use the default credentials for the proxy but I'm not at my computer to point you to it. Will try to later 🙂 |
You can see how it was added to sleet (following my request): |
@mungojam Ah, so its the auth side that's the problem, not the use of the proxy itself. That makes sense. Thanks for the link. We've already got default cred support for the APIs themselves, It should be easy to add the call for the proxy too. Looks like we'll need a new preference (probably I'll see if we can sneak that in before 5.0 |
We are behind a corporate proxy and so the tool isn't currently usable for us which is a shame as it's great :)
The text was updated successfully, but these errors were encountered: