ext/curl: Fix CURLOPT_PREREQFUNCTION
to not continue on error conditions
#16790
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a follow-up to GH-13255.
When the
CURLOPT_PREREQFUNCTION
callback does not return any value or return an invalid value, we throw aValueError
or aTypeError
exception. However, it does not prevent the Curl request from going forward because our default return value isCURL_PREREQFUNC_OK
.This changes the default value to
CURL_PREREQFUNC_ABORT
.