Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for proxy settings per collection #4739

Open
basovnik opened this issue Jun 27, 2018 · 18 comments
Open

Add support for proxy settings per collection #4739

basovnik opened this issue Jun 27, 2018 · 18 comments

Comments

@basovnik
Copy link

It would be nice to support proxy settings per collection. We might have only some collections which need proxy.

@numaanashraf
Copy link
Member

Thanks for the suggestion @basovnik. We'll take this into consideration while we improve our support for proxies.

@kenlyon
Copy link

kenlyon commented Apr 17, 2019

Yes, this would be handy. I'm working on writing a proxy, and only the requests related to that project would need my proxy settings. Switching the Global Proxy Configuration or off while switching between projects is a bit of a nuisance, and is easy to forget when the pressure is on!

@frank-adler
Copy link

We need this, too. 👍

@teunis90
Copy link

We need this too, missed this issue. I've requested the same thing in #7285

In addition, as mentioned in #7285, this feature would be an alternative and more powerful implementation of:

Hope this will be implemented soon!

@dresh
Copy link

dresh commented May 9, 2020

yes, can we get this please?

@JonasMatos0
Copy link

Having proxy per collections would really be handful.
That does prevent automating tests through postman in scenarios in which external tokens are needed for local environment setup.

@michabbb
Copy link

2 years later... i would be happy to see this too, it makes no sense to configure a proxy only global....
actually, it needs to be set by collection and even by request to override it in case the call is special....

- global (like now)
 |-> collection (missing)
   |-> request (missing)

@bduteh
Copy link

bduteh commented Oct 29, 2021

Is there any progress on this issue? It is much needed

@herenickname
Copy link

I join, necessary feature

@teunis90
Copy link

I have the feeling this is not an easy feature. It would be appreciated if we at least get feedback if this feature is planned or won't/can't be implemented.

@chrs-myrs
Copy link

This would be highly useful. Or if not this then maybe a whitelist of domains for which the proxy is only active. We are using the proxy to get around IP whitelists, so it only applies to some collections.

@moehawamdeh
Copy link

moehawamdeh commented Oct 7, 2022

This is a great feature that is missing from Postman, my suggestion is to also have it enabled in pre-request script.

Or at least allow negated bypass in the global config
E.g
!*.github.com
To allow proxy on requests to Github domain

@mohammadmazen
Copy link

It's much needed issue, hope it will added soon!

@j5shi
Copy link

j5shi commented Oct 13, 2022

Can't believe it's still missing...need it so badly...

@mottersheadt
Copy link

Hey Postman team - this would be incredibly valuable. Please add support!

@Uj947nXmRqV2nRaWshKtHzTvckUUpD

it s been 5 years and no progress on this basic feature.. what is happening?

@eprothro
Copy link

eprothro commented Aug 7, 2023

👍🏼 for our team as well.

An update from the Postman team or closing this issue would be helpful!

@fappaz
Copy link

fappaz commented May 21, 2024

Need this as well, though would prefer supporting proxy per collection as it's even more flexible.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests