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

Improve support for different proxy authentication types #216

aviast opened this issue Apr 10, 2015 · 0 comments

Improve support for different proxy authentication types #216

aviast opened this issue Apr 10, 2015 · 0 comments


Copy link

aviast commented Apr 10, 2015

The use_proxy() function does not include an argument to specify the type of authentication; please allow proxyauth to be specified here. The values for the type argument to authenticate() are all valid for the proxy authentication.
If a user chooses to configure the proxy settings with the config() function, then an "integer/logical" type is expected. My preference would be to allow character values so this setting can use the same values as mentioned above; the alternative being that a variable would need to be defined for each authentication option so that the numeric values can be supplied.
When a client sends a GET request the proxy responds with 407 (Proxy authentication required) and a header Proxy-Authenticate with value NTLM. I would expect libcurl could use this to automatically handle NTML proxy servers? (According to the docco libcurl defaults to CURLAUTH_BASIC, not CURLAUTH_ANY.)

@hadley hadley closed this as completed in 7ff8b77 May 4, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
None yet

No branches or pull requests

1 participant