+1. I wasted a lot of time not realizing Postman was adding other cookies to my request. The scenario is the following: I was testing a request on this url:
https://model.api.mycompany.com/v1/blah-api
I sent some cookies with the request to test the authentication handshaking.
Turns out postman had access to cookies from the parent domain (captured from my browser maybe or from other requests? not sure but I never set these) on the PARENT domain mycompany.com and was sending them in the “temporary headers” section. These cookies were interfering with or hiding the cookies I was trying to send.
I figured out that you can go to the “Manage cookies” dialog and delete cookies for each domain. However, my company has a lot of domains and subdomains so this list is very large. In this case, the domain is about half way down a list of like 30 domains. That means every time I do a request, I have to scroll down and search for this domain to see if any cookies are remembered. I can’t seem to find a way to do any of the following to make it easier:
- Stop storing or sending cookies other than what I’ve specified in the request
- Stop remembering cookies or at least stop remembering for certain domains
- Delete all cookies from all domains
- A search function to find the domain in the “Manage cookies” window so I can least find this domain easier
- Stop sending temporary headers, the subject of this thread
