Custom HTTP cookies are useful when your synchronization client interacts with a third-party tool, such as an authentication
proxy, or gateway and authenticates itself. If successful, the agent receives one or more cookies from the server. The agent
then starts a synchronization and hands over its session cookies through the set_cookie option.
If you have multiple name-value pairs, separate them with commas.