TLDR; to configure Postman native client app to use a proxy: use Settings to configure specific or global proxy or start it with command line parameter -proxy-server=host:port
This post updated 20170911 to describe the new Settings options in Postman to configure the Proxy.
One of things I like about Postman Chrome App is that, because it uses Chrome, it is really easy to feed through a debug proxy like Fiddler, or Zap, etc. etc.
But since Chrome Apps are going to die and Postman has a native app now, I thought I’d use that.
Uh oh! Where is the proxy setting?
There is a strange little satellite icon for “Proxy Settings” which lets me switch on an inbuilt proxy:
That might be useful. I might want to send browser traffic to postman to build up a collection. I can’t imagine doing that, but it might be useful.
What about an external proxy?
- Previous versions of Postman only supported configuration of the proxy from the command line - see below.
- Then Postman supported “System Proxy” Proxies e.g. Fiddler, or Charles which intercept all networks traffic automatically
- In version 5.2.0 Postman introduced actual Proxy configuration settings
Go to “File \ Settings” and Select “Proxy”
Then you can Toggle between:
- no proxy (both global and system set to Off)
- Global Proxy Configuration (use a specific ip address and port to proxy requests)
- Use System Proxy (use the current operating system proxy settings e.g. Fiddler, or Charles automatically)
To use the command line, the Answer Is…
And the answer is that since Postman is an electron based application we can use the electron command line switches.
Here’s how I do it on Windows.
I have a short cut with the target:
OR I could go to the postman directory and run the command:
Update 17/8/2017 - On YouTube David Porter left a comment about using this approach on a Mac:
open /Applications/Postman.app --args --proxy-server=localhost:8888
Hope that helps.