Skip to content

setopt: allow CURLOPT_INTERFACE to be set to NULL #14629

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

Closed
wants to merge 4 commits into from

Conversation

bagder
Copy link
Member

@bagder bagder commented Aug 21, 2024

Ref: #14299 (comment) Regression from 3060557 (shipped in 8.9.0)

bagder added 2 commits August 21, 2024 11:08

Verified

This commit was signed with the committer’s verified signature.
infinisil Silvan Mosberger
Ref: #14299 (comment)
Regression from 3060557 (shipped in 8.9.0)
@github-actions github-actions bot added the tests label Aug 21, 2024
@uninsane
Copy link

rebuilt curlftpfs with this patch applied to curl, and confirmed that this fixes the linked issue.

@bagder bagder closed this in b0b4b48 Aug 21, 2024
@bagder bagder deleted the bagder/interface-null branch August 21, 2024 12:34
bagder added a commit that referenced this pull request Aug 22, 2024
Previously this test allowed several error values when setting options.
This made this test miss #14629.

Now, errors are generally not accepted for setopts:

 - numerical setopts accept CURLE_BAD_FUNCTION_ARGUMENT for funny input
 - the first setopt to an option accepts CURLE_NOT_BUILT_IN or
   CURLE_UNKNOWN_OPTION for when they are disabled/not built-in
 - there is an allowlist concept for some return code for some variables,
   managed at the top of the mk-lib1521.pl script

In curl.h: remove the OBSOLETE named values from the setopt list.

Closes #14634
bagder added a commit that referenced this pull request Aug 23, 2024
Previously this test allowed several error values when setting options.
This made this test miss #14629.

Now, errors are generally not accepted for setopts:

 - numerical setopts accept CURLE_BAD_FUNCTION_ARGUMENT for funny input
 - the first setopt to an option accepts CURLE_NOT_BUILT_IN or
   CURLE_UNKNOWN_OPTION for when they are disabled/not built-in
 - there is an allowlist concept for some return code for some variables,
   managed at the top of the mk-lib1521.pl script

In curl.h: remove the OBSOLETE named values from the setopt list.

Closes #14634
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

None yet

2 participants