Cookie Jar saves browser cookies that are set by servers and can then automatically update requests with latest cookies so that they carry the up-to-date session data and are correctly authenticated to the remote web application.

Adding cookies to jar

Cookie Jar looks for cookies set by server responses in Set-Cookie headers. Details of each cookie get automatically filled based on attributes found in the header. Cookies can overwrite existing ones in the jar.

Server responses in the following tools can update Cookie Jar:

You can manually add new cookies to Cookie Jar and edit existing cookies.

Updating cookies to requests

If enabled, cookies can be automatically updated to requests before sending them to target server. You can find an option for updating cookies in each tool.

Cookies are added to requests according the following rules:

  • Domain-Matching: The request domain matches the cookie’s domain rules. Host-Only cookies must match the request domain. Non Host-Only cookies must match or be a parent of the request domain.
  • Path matching: The cookie Path must match or be a parent of the request path.
  • Expiration: The cookie has not expired.

Note that Secure or SameSite attributes are not taken into account by Cookie Jar.

Restore from history

Cookie Jar can restore cookies from current History tool messages and add them to the jar. Existing cookies can get updated in the process.