Hi – I really like postman but still use it as a chrome web app. The key feature that keeps me using postman as a chrome app and not migrating to the native app is the combination of postman with SwitchyOmega (or any other similar proxy tool) – in general I often need to tunnel requests over different SOCKS5 tunnels based on the destination host; with postman under chrome that has SwitchyOmega installed this works seamlessly (e.g. once the patterns are set up a request to http://host1/api1… will automatically go via a socks tunnel at port “1111” but http://host2/api2… will automatically go via port “2222” while a url with no pattern will go direct). Do either the native or new web postman support this mode of operation?
Thank you!
Can you please explain a bit how do you use Socks5 and postman, I’m getting
"
Error
tunneling socket could not be established, cause=socket hang up
"
@aviation-geologist-9
This should have been its own question, as its not really related to the proxy server question posted by the original poster.
The error you are having is a communication one, so its not Postman specific.
You can confirm this by running your request using another application\method like curl. (You have code snippets to the right hand side of a request where it would give you the curl command that you can copy and paste).
This sounds like a config issue with your proxy\firewall. If you are using Windows, you might also need to check the local firewall settings to ensure that isn’t blocking anything. (Particularly if you are using non-standard ports).