It will force libcurl to ignore all cookies it is about to load that are "session cookies" from the previous session.
By default, libcurl always stores and loads all cookies, independent if they are session cookies or not.
Session cookies are cookies without expiry date and they are meant to be alive and existing for this "session" only.
This allows you to have a libcurl built to support a wide range of protocols but still limit specific transfers to only be allowed to use a subset of them.
By default libcurl will accept all protocols it supports. This allows you to limit specific transfers to only be allowed to use a subset of protocols in redirections.
By default libcurl will allow all protocols except for FILE and SCP.
This is a difference compared to pre-7.19.4 versions which unconditionally would follow to all protocols supported.
See also 1 to check the existence of a common name in the SSL peer certificate.
2 to check the existence of a common name and also verify that it matches the hostname provided.
In production environments the value of this option should be kept at 2 (default value).
The maximum number of milliseconds to allow c URL functions to execute.
If libcurl is built to use the standard system name resolver, that portion of the connect will still use full-second resolution for timeouts with a minimum timeout allowed of one second.
If a download exceeds this speed (counted in bytes per second) on cumulative average during the transfer, the transfer will pause to keep the average rate less than or equal to the parameter value. If an upload exceeds this speed (counted in bytes per second) on cumulative average during the transfer, the transfer will pause to keep the average rate less than or equal to the parameter value. Allows an application to select what kind of IP addresses to use when resolving host names.
This is only interesting when using host names that resolve addresses using more than one version of IP, possible values are The name of the file containing the cookie data.