I've noticed the following behavior with cookies initialization which looks
a bit inconsistent to me. If one initializes a plain-vanilla easy handle
without setting any special cookie options, the SessionHandle cookies
pointer is 0. However, if one uses CURLOPT_SHARE, then the cookies pointer
is initialized. This happens regardless of the share specific options, i.e.
regardless of whether the share manages cookies or not.

Does this matter? I'm not sure. Presumably there are no side affects, other
than invoking curl's cookie handling functions, but I could be missing
something...

Oh, I'm using curl 7.16.4 .

Cheers,
Shmul
Received on 2007-07-29