Daniel Stenberg
Daniel Stenberg
Since this is a build option and not even set by default, I am in favor of it. curl users on all platforms are used to `curl https://host` using the...
> There's no reason to the change the user's --cacert choice. No there isn't. I wasn't aware this did. --cacert should override the default. I was under the impression that...
@michael-o don't mixup native-ca and "ca-fallback" though. The first one uses "the native CA store" (which primarily is a thing on Windows and macOS) while the second option more mysteriously...
I'm generally skeptical of this command line option. - this operation can mostly be done already by just crafting the right set of options - it introduces a state for...
> I think I understand why curl behaves this way, but I would have expected to have a 'safe' default of GET restored when setting CURLOPT_POST to 0, as this...
> But it would be nice to have it documented that CURLOPT_CUSTOMREQUEST takes precedence I think it already does. It explicitly says: > When changing the request method by setting...
I would still be happy if you you could maybe show with an example or be more specific because I think it already says all it can say. CURLOPT_POST makes...
> Would you be open to a PR where I add a small 'Note' or warning in CURLOPT_POST.3 clarifying this? It might save other users from this confusion. Sure. If...
This looks like an oversight in the code, yes.
Unless you provide us with traces showing more details we can't tell exactly where the problem lies and if there is something for us to fix. Sticking to an old...