Cookies

Cookies

Getman keeps a persistent cookie jar so session-based auth just works across requests — like a browser, but under your control.

How the jar works

• Stored automatically: Set-Cookie headers from responses are parsed and saved, keyed by domain | path | name (a new value for the same key replaces the old one).
• Sent automatically: before each request, matching cookies are attached to the Cookie header. Matching follows the usual rules — domain (exact or subdomain), path prefix, Secure (HTTPS only), and expiry (expired cookies are skipped).
• Persistent: the jar survives restarts (stored locally; see Data Privacy and Storage).

You can also see the cookies a single response set in the Responses.

The cookie manager

Open Settings → COOKIES → MANAGE to inspect and prune the jar.

• Cookies are grouped by domain (alphabetical), then by name/path.
• Each cookie shows name = value and its flags: path=…, Secure, HttpOnly, and session (no expiry).
• Delete one: click the trash icon on a cookie ("Delete cookie?" confirm).
• Clear all: the CLEAR ALL button wipes the whole jar ("Clear cookies?" confirm).

There's also a CLEAR button directly in the Settings COOKIES row to empty the jar without opening the manager.

Tips

• If a server keeps rejecting you after a logout/login change, clear the relevant cookies in the manager.
• Cookies are matched per-URL, so the same jar serves multiple hosts safely.