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

CURLOPT_NOBODY.3: clarify what setting to 0 means #5729

Closed
wants to merge 1 commit into from

Conversation

@bagder
Copy link
Member

bagder commented Jul 27, 2020

... and mention that HTTP with other methods than HEAD might get a body and
there's no option available to stop that.

... and mention that HTTP with other methods than HEAD might get a body and
there's no option available to stop that.
For HTTP operations when \fBCURLOPT_NOBODY(3)\fP has been set, unsetting the
option (with 0) will make it a GET again - only if the method is still set to
be HEAD. The proper way to get back to a GET request is to set
\fBCURLOPT_HTTPGET(3)\fP and for nother methods, use the POST ur UPLOAD

This comment has been minimized.

Copy link
@causal-agent

causal-agent Jul 27, 2020

Suggested change
\fBCURLOPT_HTTPGET(3)\fP and for nother methods, use the POST ur UPLOAD
\fBCURLOPT_HTTPGET(3)\fP and for other methods, use the POST or UPLOAD
@bagder bagder closed this in e1bac81 Jul 27, 2020
@bagder bagder deleted the bagder/nobody-clarify branch Jul 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

2 participants
You can’t perform that action at this time.