SOCKS5

[pierreprinetti]

Is it possible to set up a specific collection to fire requests through a pre-existent SOCKS proxy?

[abhijitkane]

This is not possible at a collection level. Postman uses Chrome's default proxy settings for all requests.

[pierreprinetti]

Do you think it is feasable to implement custom proxy rules internally?

[abhijitkane]

Not sure. We'll look into this.

[pierreprinetti]

Thank you! Very useful project, no regrets since purchase.

[strobelight]

So, this implies Chrome must be running in order for the standalone Postman app to work? Guess I'm ok with that, just doesn't sound like a standalone app.

But, I do need to access an API via a SOCKS5 proxy, somehost:9999. Works fine when the Chrome Postman app runs, since it uses my Chrome extension SwitchyOmega. Haven't been able to figure out how to get the standalone OSX Postman app to use it.

[splagemann]

Are there actual plans that this will be implemented?

[polomsky]

It would be fine to have different proxy settings for each environment (e.g. for live no proxy, for devel proxy)

[fostec82]

Is there a timeline on this feature?

[onionsheep]

i wanna this feature too

[xingchen19]

Without this feature, I have to give up using native postman and continue for Chrome app.

[burlacio]

Hope you can integrate this before the Chrome apps are deprecated

[aaneez]

This is still open..Any plans to fix this?

[PBXg33k]

Could this get a higher priority now that the Chrome extension has been removed.

In our situation we cannot use postman to test our APIs because we need to use SOCKS proxies setup using SSH tunnels in order to access the servers

[tangyl]

I end up using privoxy as http=>socks5 proxy. It can forward requests to different socks5 proxies by host patterns. e.g.

forward-socks5t a1* 127.0.0.1:1088 .
forward-socks5t a2* 127.0.0.1:1088 .
forward-socks5t a3* 127.0.0.1:1088 .
forward-socks5t sg-* 127.0.0.1:1090 .

[actopolus]

When should we expect this feature? Are you working on it?

[Skeeve]

I'm also eagerly awaiting this feature :(

[Skeeve]

FTTB I switched to FoxyProxy + RESTClient (both FireFox extensions) to test and debug the webservices I work with.

[AnthonyRinaldi]

When will this be fixed? This is a hard stop for using Postman.

[mortac8]

Also would like SOCKS support. Very important for us.

[marpo60]

In the mean while you could do a local tunnel.

ssh -L 9999:destination.com:80 sock5_proxy_server

Use localhost:9999 in your postman address and it will be the same as accessing destination.com:80 from the sock5_proxy_server

https://www.ssh.com/ssh/tunneling/example

[Skeeve]

Nope. In the meantime I can more easily use RESTClient + FoxyProxy because for this I do not have to change any url.

To be honest: I find it much more convenient and I do not miss Postman at all.

[rmatec]

Can we assume this will never be implemented?

[navennn]

SSH tunnelling works. ssh -L 12345:192.168.1.15:80 your-external-ip in postman as dest you specify localhost:12345 Make sure proxy is disabled in the settings.

[Skeeve]

@navennn you totally missed the point. This is about socks5 proxy.

With that you have a socks 5 proxy which will forward any traffic to any target host.

Normal tunneling forwards traffic to one specific target host.

[navennn]

I know. But this is a workaround to your issue. At least you can do it.

[Skeeve]

And @navennn you also missed the fact that there already is a much better workaround. Additionally your "tipp" already was given by @marpo60.

[navennn]

I read all of it, I know. You can't prove me wrong since I'm not wrong.

[pierreprinetti]

@Skeeve

Unless @navennn is representing @postmanlabs, I see no reason for being aggressive.

[Skeeve]

Okay, @pierreprinetti - I'm out. No more interest in Postman.

[pierreprinetti]

Okay, @pierreprinetti - I'm out. No more interest in Postman.

Just to clarify: nobody in this thread works for Postman AFAIK, except @abhijitkane. People are just trying to help.

That being said, bye bye @Skeeve!