Cookies

FleetFoot keeps the cookies that servers set and sends them back with the next requests to the same site, like a browser. Log in once, and the requests after it carry the session.

How it works

• A Set-Cookie header in a response puts the cookie into the cookie jar. Cookies set during redirects are kept too.
• Every request gets the cookies that match its address: the domain (with subdomains, when the cookie allows it), the path, and https for secure cookies.
• When a server deletes a cookie or it expires, it leaves the jar.
• Session cookies (without an expiry date) are kept until you delete them, also across restarts.

A Cookie header you add yourself is sent too: FleetFoot joins it with the cookies of the jar into one header. When both have a cookie with the same name, yours wins.

Open the Headers tab of a request and expand Headers added automatically to see which cookies it will send.

Cookies of a response

The Cookies tab of a response lists the cookies the server set, with their domain, path, expiry and flags. It also says how many cookies were saved to the jar or removed from it.

Manage cookies

Open the cookie manager from Request → Cookies… in the menu, Manage cookies… in the Cookies tab of a response, or ⌘K → Manage cookies…. Opened from a request, it shows the cookies of its domain.

• Pick a domain on the left, or All domains.
• Click a cookie to change its value, path, expiry or flags.
• Add cookie creates one by hand, for example a session copied from a browser.
• Delete one cookie with the bin button, or all cookies of a domain at once.

Turn cookies off

To stop keeping and sending cookies everywhere, turn off Settings → Requests → Cookies.

For one request, open its Settings tab and set Cookie jar to Off: the request sends no cookies from the jar and saves none. On turns the jar on for that request even when it is off in the app settings.

The Postman setting Disable cookie jar of a request comes over with the import and goes back with the export.