Skip to content

CURLE_PROXY: new error code#5770

Closed
bagder wants to merge 1 commit intomasterfrom
bagder/proxy-error
Closed

CURLE_PROXY: new error code#5770
bagder wants to merge 1 commit intomasterfrom
bagder/proxy-error

Conversation

@bagder
Copy link
Copy Markdown
Member

@bagder bagder commented Aug 3, 2020

Failures clearly returned from a (SOCKS) proxy now causes this return
code. Previously the situation was not very clear as what would be
returned and when.

In addition: when this error code is returned, an application can use
CURLINFO_PROXY_ERROR to query libcurl for the detailed error, which then
returns a value from the new CURLproxycode enum.

@bagder bagder added feature-window A merge of this requires an open feature window connecting & proxies libcurl API labels Aug 3, 2020
Failures clearly returned from a (SOCKS) proxy now causes this return
code. Previously the situation was not very clear as what would be
returned and when.

In addition: when this error code is returned, an application can use
CURLINFO_PROXY_ERROR to query libcurl for the detailed error, which then
returns a value from the new 'CURLproxycode' enum.

Closes #5770
@bagder bagder force-pushed the bagder/proxy-error branch from d251547 to 52ad36d Compare August 4, 2020 13:58
@bagder bagder marked this pull request as ready for review August 19, 2020 13:57
@bagder bagder closed this in 88b1ca7 Aug 24, 2020
@bagder bagder deleted the bagder/proxy-error branch August 24, 2020 06:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

connecting & proxies feature-window A merge of this requires an open feature window libcurl API

Development

Successfully merging this pull request may close these issues.

2 participants