CURLINFO_COOKIELIST man page example: non-existing file is stdin

[3dyd]

Hello,

From CURLINFO_COOKIELIST example:

/* enable the cookie engine with a non-existing file */
curl_easy_setopt(curl, CURLOPT_COOKIEFILE, "-");

But "-" stands for stdin, isn't it?

[jay]

Thanks

[3dyd]

Also could you satisfy my curiosity?

Documentation of curl_easy_getinfo says:
The data pointed-to will be filled in accordingly and can be relied upon only if the function returns CURLE_OK.

So in this part of example:

res = curl_easy_getinfo(curl, CURLINFO_COOKIELIST, &cookies);
if(!res && cookies) {
  ...
  curl_slist_free_all(cookies);
}

Why one would need to check that cookies != NULL?

If "just in case", then why not to be consistent and go further with

res = curl_easy_getinfo(curl, CURLINFO_COOKIELIST, &cookies);
if(!res && cookies) {
  ...
}
if(cookies) {
  curl_slist_free_all(cookies);
}

[jay]

The documentation for the specific option always takes precedence, however in this case there is no conflict. If curl_easy_getinfo returns CURLE_OK then cookies was written to but is NULL if there were no cookies.

[3dyd]

Perfect. Thank you.