set_cookie=cookie-name=cookie-value,...

• HTTP, HTTPS

None

Custom HTTP cookies are useful when your synchronization client interacts with a third-party tool, such as an authentication tool, that uses cookies to identify sessions. For example, you have a system where a user agent connects to a web server, 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.

For information about how to set network protocol options with dbmlsync, see CommunicationAddress (adr) extended option.

For information about how to set network protocol options with UltraLite, see Network protocol options for UltraLite synchronization streams.

The following example sets two custom HTTP cookies in an embedded SQL or C++ UltraLite application.

info.stream = "http";
info.stream_parms = 
  "host=www.myhost.com;
  set_cookie=MySessionID=12345, enabled=yes;";