SOCKS5 - Githubissues

pierreprinetti commented 9 years ago

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

abhijitkane commented 9 years ago

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

pierreprinetti commented 9 years ago

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

abhijitkane commented 9 years ago

Not sure. We'll look into this.

pierreprinetti commented 9 years ago

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

strobelight commented 8 years ago

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 commented 8 years ago

Are there actual plans that this will be implemented?

polomsky commented 7 years ago

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

fostec82 commented 7 years ago

Is there a timeline on this feature?

onionsheep commented 7 years ago

i wanna this feature too

xingchen19 commented 7 years ago

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

burlacio commented 7 years ago

Hope you can integrate this before the Chrome apps are deprecated

aaneez commented 6 years ago

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

PBXg33k commented 6 years ago

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 commented 6 years ago

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 commented 6 years ago

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

Skeeve commented 6 years ago

I'm also eagerly awaiting this feature :(

Skeeve commented 6 years ago

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

AnthonyRinaldi commented 6 years ago

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

mortac8 commented 6 years ago

Also would like SOCKS support. Very important for us.

marpo60 commented 6 years ago

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 commented 6 years ago

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 commented 6 years ago

Can we assume this will never be implemented?

navennn commented 6 years ago

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 commented 6 years ago

@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 commented 6 years ago

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

Skeeve commented 6 years ago

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

navennn commented 6 years ago

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

pierreprinetti commented 6 years ago

@Skeeve

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

Skeeve commented 6 years ago

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

pierreprinetti commented 6 years ago

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!

mortac8 commented 6 years ago

I just reverted to using the postman chrome app then set the socks proxy in my browser.

Prestaul commented 6 years ago

FWIW, I found a kanban board in this project with proxy related issues on it. Not really much insight there but I think this is were this work would be tracked (if it were in flight)...

miqueet commented 6 years ago

Curious if socks 5 proxy is going to be implemented into the standalone app. Since this appears to be a port from chromium via electron it should be able to set its own socks 5 proxy.

Since it looks like this is available in electron and is documented well it shouldn't be difficult to implement. https://github.com/electron/electron/blob/a0cac0555570b1c55d011d72e32f48ef6e0c9e28/docs/api/session.md

avmohan commented 6 years ago

A workaround to this issue is to convert the socks proxy into an http proxy using https://github.com/oyyd/http-proxy-to-socks

bloigge commented 6 years ago

@avmohan - thanks for sharing. that's the most easy solution. great tool!

mihaimorcov commented 6 years ago

Any plans to have this feature implemented? Will the existent Chrome app stay functional or should we expect it to be unusable after a point?

arkhoss commented 5 years ago

I would love to see this feature in Postman, tip: "take a look of SwitchyOmega Chrome extension", if Postman can do that... would be really powerful and support proxy settings for multiple profiles / envs.

thanks!

mancubus77 commented 5 years ago

A workaround to this issue is to convert the socks proxy into an http proxy using https://github.com/oyyd/http-proxy-to-socks

+1 But doesn't work for host:ip Switched to Chrome extension, which works smooth with browser config.

anandmatti commented 5 years ago

A workaround to this issue is to convert the socks proxy into an http proxy using https://github.com/oyyd/http-proxy-to-socks

Does this work with https urls?

dvershinin commented 4 years ago

Awesome tip by @tangyl about using Privoxy. Basically it can "add" SOCKS5 support to any app which doesn't natively support SOCKS5. Documented my experience with Postman + Privoxy here.