Note: Advice in this article will only work for DotNetBrowser 1.
See the corresponding article for DotNetBrowser 2 here.

DotNetBrowser delegates work with cookies to Chromium engine. Chromium engine decides how to download cookies from a web server, extract them from HTTP headers and store them on a local file system (persistent cookies) or memory (session cookies). By default DotNetBrowser doesn't modify Chromium's behavior, so support of cookies is enabled by default.

To work with cookies, DotNetBrowser provides CookieStorage and Cookie classes. Using CookieStorage you can access the actual cookie storage to get, modify or remove cookies. The Cookie class allows you to get information about specified cookie.

Supported Protocols

DotNetBrowser supports cookies that are sent using the following protocols:

  • HTTP
  • WS (WebSocket)
  • WSS (Secured WebSocket)

If the cookie is sent using a protocol that isn't in the list (e.g. ftp://), then they will not be stored in the storage.