You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
reading the manpage for CURLOPT_HTTPGET, it is unclear to me whether if is ever necessary/useful to pass a value other than 1 for "useget"
Some possibilities occur to me:
You should do a setopt for CURLOPT_HTTPGET with useget of 0 whenever you switch from GET to POST or another method, and aren't doing curl_easy_reset()
You don't need to do a setopt for CURLOPT_HTTPGET when switching from GET to POST because setting CURLOPT_POST or the equivalent for other methods automatically sets CURLOPT_HTTPGET to 0.
If you need to set CURLOPT_HTTPGET to 0, you're doing things wrong and should be calling curl_easy_reset() more often.
It would be useful if the CURLOPT_HTTPGET manpage contained documentation about this. Probably only a single added sentence would do.
I suspect this suggestion is applicable to the manpage for CURLOPT_POST as well.
The text was updated successfully, but these errors were encountered:
reading the manpage for CURLOPT_HTTPGET, it is unclear to me whether if is ever necessary/useful to pass a value other than 1 for "useget"
Some possibilities occur to me:
It would be useful if the CURLOPT_HTTPGET manpage contained documentation about this. Probably only a single added sentence would do.
I suspect this suggestion is applicable to the manpage for CURLOPT_POST as well.
The text was updated successfully, but these errors were encountered: