Setting up Postman with QG Shield & QG Static
Table of contents
Let’s get the bad news out of the way first…unfortunately, Postman does not support HTTPS proxies. Since QuotaGuard Shield is an HTTPS proxy, we’re out of luck to use Shield.
However, Postman does supports HTTP proxies - which allow HTTP and HTTPS traffic through them. Thankfully, QuotaGuard Static is an HTTP proxy.
To make this work, you need to run Postman using our QGPass software.
QGPass opens up an unathenticated HTTP proxy locally that Postman can then connect to. Then, QGPass sends the traffic onwards to our proxies using HTTPS.
Here’s how to get this working:
Download QGPass.
For linux
curl https://s3.amazonaws.com/quotaguard/qgpass-latest.tar.gz | tar xz
For mac:
curl https://quotaguard.s3.amazonaws.com/qgpass-1.1.0-darwin.tar.gz | tar xz
Run qgpass.
QUOTAGUARDSHIELD_URL={your connection url} ./bin/qgpass sleep 100000
Run Postman.
In Postman, connect to a proxy (no username/password) at localhost on port 8080.
If you hit any snags, as always, reach out to us at Support.
Happy Tunneling!