Cookie control with collection runs

[nlwillia]

I'm testing with a service that sets an unwanted session cookie in the response. If I visit that service in Postman, the cookie is being saved and replayed for later requests.

I've identified several ways to submit a new request without the cookie...

1. Implement a reset feature in the service that clears the cookie and request it from Postman before making a new service request from the domain/path. (This is not an option if dealing with a 3rd party service.)
2. Route requests through a proxy that strips the Set-Cookie response header.
3. Exit Postman and all instances of Chrome including the background process that Chrome runs in the Windows notification area if the "Continue running background apps when Google Chrome is closed" browser setting is checked. Then restart. (Don't think this would work for a non-session cookie.)
4. Install and enable the Interceptor plugin so that the browser's cookie store is used. Open Chrome to chrome://settings/cookies and manually remove the unwanted cookies before each request. Setting the Cookie header manually from within Postman in Interceptor mode can override the cookie that is sent (Cookie: unwanted-cookie=), but not remove it from the request completely.

None of these are very convenient. Is there a better way to forcibly disable any sort of cookie header being sent?

edit: 2018-04-20 This was originally logged against the Chrome app which has since been deprecated in favor of the native apps. The native apps don't appear to have the same browser-level constraint that made cookie management in Chrome a non-starter. There's now a Cookies link that pops a MANAGE COOKIES modal where cookies can be added or removed. This is an improvement as it's now possible to directly remove an unwanted cookie. Unfortunately there still doesn't seem to be a way to disable cookies entirely. However, the Pre-request Script option is promising as a way to run script to configure things that aren't supported in the UI. This does not appear to support cookie manipulation, but there's a recent issue suggesting it. If that's possible and gets done, then that will become a way to (finally) address this use case.

An aside to all the +1-ers out there, Github has had reactions for over 2 years now; please use them!

[richarddavenport]

I agree. I would love to be able to see the cookies and clear or edit them.

[b0elter]

+1

[abhijitkane]

This is currently a limitation of the Chrome platform - packaged apps do not have access to Cookies that have been set, nor is there a way to edit/delete them. There are 2 bugs filed on crbug - https://code.google.com/p/chromium/issues/detail?id=236585, https://code.google.com/p/chromium/issues/detail?id=152758

Still waiting for a response on these.

[dbalabka]

+1 . My current solution is:

1. Open any page on the same domain in GoogleChrome
2. Open Developer tools(F12)
3. In Developers tool tab Resources clear all cookies before each request 😄 It's very annoying but works
   

+1 to have the option to send a request without cookies.

[philals]

+1

[tobilarscheid]

+1

[divayprakash]

+1

[akirayamamoto]

+1

[PiWhy]

+1

[lshapsa]

+1

[cychai]

+1

Postman v0.9.6 – Access cookies and restricted headers. Plus better tests!