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

Need for proxy ignore/bypass feature #1791

Closed
wengxuan opened this issue Sep 18, 2017 · 9 comments
Closed

Need for proxy ignore/bypass feature #1791

wengxuan opened this issue Sep 18, 2017 · 9 comments
Assignees
Labels
STATE: Auto-locked An issue has been automatically locked by the Lock bot. TYPE: enhancement The accepted proposal for future implementation.
Milestone

Comments

@wengxuan
Copy link

wengxuan commented Sep 18, 2017

Are you requesting a feature or reporting a bug?

feature

What is the current behavior?

For individual devoloper at home, it's enough to have basic proxy settings as document discribe. We can set proxy host, port and also auth.
https://devexpress.github.io/testcafe/documentation/using-testcafe/command-line-interface.html#--proxy-host

What is the expected behavior?

However, when you work in a company, you have to visit the internet through company's intranet. There exist some limitations. Some sites only can visit from inside network, and others need to use proxy.
In IE LAN Setting, we can set proxy, port and address not use proxy. So can we add an issue of proxy --ignore/bypass ?
I saw Issue1206 had mentioned this feature, but for some reason not added.
Guys, if you have this needs, add your comments under this issue. Thank you.

Long live testcafe! xD

@AlexanderMoskovkin
Copy link
Contributor

AlexanderMoskovkin commented Sep 18, 2017

Hi @wengxuan,

Thanks for your proposal. We'll consider it when planning our future releases. Those of you who are interested in this feature, feel free to vote for it and leave your comments.

@n0v1
Copy link

n0v1 commented Oct 24, 2017

We also have to use a corporate proxy to access some ressources but our backend is only accessible directly without proxy. It would be ideal if Testcafe would respect the NO_PROXY environment variable or had an equivalent option.

@AlexanderMoskovkin AlexanderMoskovkin added TYPE: enhancement The accepted proposal for future implementation. and removed TYPE: proposal labels Oct 24, 2017
@AlexanderMoskovkin AlexanderMoskovkin added this to the Sprint #10 milestone Oct 24, 2017
@AlexanderMoskovkin
Copy link
Contributor

Thanks for your feedback. I guess we'll consider it on the next release planning soon

@raDiesle
Copy link

raDiesle commented Jan 3, 2018

Great, otherwise I cannot develop in company network

@maximgeerinck
Copy link

Also looking forward to this, can not access local resources without

@AlexKamaev
Copy link
Contributor

closed in #2187

@AlexKamaev AlexKamaev reopened this Mar 12, 2018
AlexKamaev added a commit to AlexKamaev/testcafe that referenced this issue Mar 13, 2018
AlexKamaev added a commit to AlexKamaev/testcafe that referenced this issue Mar 14, 2018
AlexKamaev added a commit to AlexKamaev/testcafe that referenced this issue Mar 16, 2018
AlexKamaev added a commit to AlexKamaev/testcafe that referenced this issue Mar 20, 2018
@AlexanderMoskovkin
Copy link
Contributor

Done in #2209

@n0v1
Copy link

n0v1 commented Apr 6, 2018

I tested the proxy bypass feature with version v0.19.2-alpha1 and it works perfectly for our use case. Thank you very much!

@lock
Copy link

lock bot commented Mar 28, 2019

This thread has been automatically locked since it is closed and there has not been any recent activity. Please open a new issue for related bugs or feature requests. We recommend you ask TestCafe API, usage and configuration inquiries on StackOverflow.

@lock lock bot added the STATE: Auto-locked An issue has been automatically locked by the Lock bot. label Mar 28, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Mar 28, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
STATE: Auto-locked An issue has been automatically locked by the Lock bot. TYPE: enhancement The accepted proposal for future implementation.
Projects
None yet
Development

No branches or pull requests

7 participants