By user2158382


2014-06-29 00:51:53 8 Comments

Ever since I upgraded to Postman 0.9.6 I can't replicate user sessions because chrome doesn't allow postman to get user cookies. However, they have decided to "work around" this issue by created another plugin called Postman Interceptor that routes your postman request and grabs the user cookies. They wrote a blog post about this wonderful tool here: http://blog.getpostman.com/index.php/2014/02/11/postman-v0-9-6-access-cookies-and-restricted-headers-plus-better-testing/

However, I can't seem to figure out how to get this thing to work. I have been trying for an hour now, and it still won't see my request as a logged in user

6 comments

@duleshi 2019-02-13 03:06:48

There are two ways, and both works:

1) postman chrome app + postman interceptor plugin

Deprecated but more convenient, just a few clicks are needed.

2) postman native app

Officially recommended by not very user friendly. You have to manually change the browser/system proxy setting.

@Michael Kropat 2018-01-26 16:03:00

To save someone having to dig through all the comments on related questions, here's a quick overview of the state of Postman in 2018:

Standalone Postman (Current)

If you have a satellite dish icon you are using standalone Postman:

postman standalone screenshot

Postman Interceptor does not appear to work with the standalone Postman (as of January 2018).

When you turn the satellite dish on, you are starting a proxy (default port: 5555). If you update your browser and/or OS proxy settings to point to localhost:5555, the requests made through the proxy will show up in Postman, similar to how it worked with the old Interceptor.

You can read more about this feature here.

Postman Chrome App (Deprecated)

If you have a weird satellite thing icon you are using the old Chrome App:

postman chrome app screenshot

This should work with the interceptor. See the instructions in nozzleman's answer if you are having trouble getting it to work.

tl;dr You need to use the Postman Chrome App if you want to use the Interceptor extension.

@zooropa 2018-03-22 20:55:27

Thank you for the answer! I was having issues with the standalone app. I notice the difference in icons. I couldn't find any info in the documentation. I just downloaded the Chrome App version of Interceptor and it displays the traffic in the History window!

@shanemgrey 2018-08-29 22:12:35

I tried the stand alone app a few times but could never figure out how to intercept the ajax traffic from my client side web app (or any traffic really) until today with the help of this answer. Thank you. FYI, there is some documentation of the feature now. Hadn't been able to find it before today. getpostman.com/docs/v6/postman/sending_api_requests/…

@shanemgrey 2018-08-29 22:28:31

Unfortunately, using Chrome on MacOS at least, it's necessary to proxy ALL HTTP and/or HTTPS traffic to capture any of it. That's a lot of trust to be putting in an app installed from binary. There is a work around described here. apple.stackexchange.com/questions/244711/… Or you can just use a different browser like Firefox which has the ability to do manual proxy config instead of using system settings.

@Michael Kropat 2018-08-30 13:06:32

Thanks @shanemgrey. I updated the answer to link to the proxy documentation.

@chovy 2019-01-21 21:50:51

How do we set the proxy on macos? I tried http, https and socks but none worked. I get invalid certificate errors.

@timetofly 2017-05-26 21:27:58

The issue for me was that I had multiple Chrome profiles, and requests with a non-main profile wasn't working, even if the extension was enabled. Once I switched to the primary profile and ensured the extension was enabled there, it started intercepting properly.

@Attie 2017-09-21 11:59:48

I think this might be affecting me... but I've installed the extension on both profiles, and it's still not working. Any ideas?

@timetofly 2017-09-21 18:22:38

@Attie did you try closing the non-main profile window and visit the website with the main profile (to share those cookies)? Try quitting chrome and starting up with just the main profile. Ensure it's enabled properly as the main answer explains: stackoverflow.com/a/41564921/371699

@Attie 2017-09-21 21:34:27

Thanks, I did many of those things. Will try again tomorrow to be sure.

@Brandon 2017-10-10 18:44:19

This is ridiculous but it was my problem.

@nozzleman 2017-01-10 09:03:17

This worked for me:

  1. Install Postman
  2. Install the Interceptor
  3. Activate the Interceptor by toggling the switch:
    enter image description here
  4. Activate the Interceptor in Postman by clicking on the Interceptor Button on the top right (looks like a sattelite)
    enter image description here

@ahyong 2017-08-07 06:31:53

After following the above 4 steps, when you request a url in chrome, you can see your request history in the Postman history tab including request headers.

@Attie 2017-09-21 12:00:18

I don't see the 'satellite' icon... any ideas?

@nozzleman 2017-09-21 12:10:49

nope, maybe you are looking at the wrong place? I just installed it freshly and i can see it in the app

@Attie 2017-09-21 21:33:46

Huh... do I need to create an account / login? It definitely wasn't there... I'll try more tomorrow.

@nozzleman 2017-09-22 06:05:50

You can proceed to the app without loggin in, the link is pretty tiny though, compared to the login options ;)

@Attie 2017-09-22 20:15:50

I think my mistake was running the standalone 'Postman' application, rather than the Chrome App... sigh thanks!

@Nahuel Barrios 2017-10-18 21:38:35

if you want to add the User-Agent header for instance you don't have to turn on the interceptor in Chrome. It's enough with installing the extension and turning on the interceptor in the Postman client. Regards!

@Jake 2016-11-09 17:31:45

Im on OSX 10.10.4 and I had to follow these instructions to allow a proxy server in order for the interceptor to work:

https://www.getpostman.com/docs/capture_native

@Ali Nikneshan 2015-12-08 20:59:22

Make sure to turn the Interceptor on in chrome and proxy on in Postman. Also ensure install correct extension! Oddly, it seems there are 2 postman Interceptor:

  1. Interceptor 1 <- Same name but not from getpostman.com
  2. Interceptor 2 <- from correct source

Then it should work

Related Questions

Sponsored Content

12 Answered Questions

[SOLVED] How do I set/unset a cookie with jQuery?

8 Answered Questions

[SOLVED] Sending cookies with postman

  • 2015-06-17 11:34:46
  • MiddleWare
  • 80516 View
  • 45 Score
  • 8 Answer
  • Tags:   cookies postman

35 Answered Questions

[SOLVED] How do I debug Node.js applications?

18 Answered Questions

[SOLVED] How to disable JavaScript in Chrome Developer Tools?

12 Answered Questions

[SOLVED] How do I expire a PHP session after 30 minutes?

  • 2009-02-06 13:14:14
  • Tom
  • 870348 View
  • 978 Score
  • 12 Answer
  • Tags:   php session cookies

12 Answered Questions

[SOLVED] How does Facebook disable the browser's integrated Developer Tools?

8 Answered Questions

[SOLVED] How to reposition Chrome Developer Tools

11 Answered Questions

[SOLVED] How to remove border (outline) around text/input boxes? (Chrome)

29 Answered Questions

[SOLVED] How do I get ASP.NET Web API to return JSON instead of XML using Chrome?

1 Answered Questions

[SOLVED] best practice for session timeouts and persistent login in php

Sponsored Content