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
Is there a way to specify a proxy server in the Config? #124
Comments
Can you show an example of this? |
You need to specify it in the |
Tried it, didn't really work for me. It could be my inexperience with it. Do you or anyone have a quick example that you can show? It would go a long way. |
|
This solution is not working for our setup. Any ideas what I'm doing wrong? I get the following error in the command line when trying to run Protractor:
Here is my config file:
|
I tried your capabilities, and it works for me. When I put in a bogus httpProxy I see 'could not connect to proxy' errors in the browser, but the tests still attempt to run. Do your tests run correctly without the proxy? How do they fail in that case? |
Okay, what I found does work is to just set the baseurl to the https testing site, like this:
|
Hi, I managed to get the proxy working with what you guys have done here so thanks for that, I now want to add in the noProxy variable so that I can exclude my internal services from going to the proxy. I have tried the following but the noProxy part isn't getting used. I am using PhantomJs.
}, |
Hi,
and
I am trying to complete https://docs.angularjs.org/tutorial/step_03, using browser Chrome. |
Doesn't work for me either - i have to provide host:port along with username/password and I tried all the above suggestions and nothing seems to be working. However, when I get off the company internet and try without proxy it all works fine. Any help? |
Actually, my problem was solved by setting up system variables
|
This needs to be re-opened, here at GE Software, setting the http_proxy and https_proxy in the configuration still does not allow Protractor to send Saucelabs the final exit code of the test results, making Saucelabs fail the test due to inactivity. |
@jonniespratley does |
I tried running protractor test on sauce lab but it getting ETIMEDOUT error. I am behind corporate firewall and I have configured proxy in protractor config file and environment variable. Configuration doesn't seems to work. Below is the error I am getting
Any idea? I will really appreciate the help. |
I am receiving similar errors. I am behind a corporate proxy and am not able to submit a test to browserstack.
|
What finally worked for us to get out of our corporate proxy and over to perfecto mobile's selenium server was using the exports.config = {
framework: 'jasmine',
seleniumAddress: 'https://yourCloudName.perfectomobile.com/nexperience/perfectomobile/wd/hub',
webDriverProxy: 'http://your.proxy.here:8080',
capabilities: { ... },
specs: ['myspec.js']
}; |
I am working behind the corporate proxy tried adding this code in conf.js it was working fine but the application execution time has increased which results failing, Yes I can increase the default time but I dont want my application to take longer time to run. Thanks in advance. |
@gregjacobs I am using webDriverProxy with perfecto as well. It was working for me for awhile back. After upgrading to 4.x or 5.x, I couldn't get it to work anymore. Does it still work for you after upgrade? |
None of the proxy options from https://github.com/angular/protractor/blob/master/lib/config.ts work for me. Anybody had luck configuring proxy in v5 ? |
@deli6z capabilities: {
'browserName': 'chrome',
'args': ['disable-web-security'],
'proxy': {
'proxyType': 'manual',
'httpProxy': '10.179.70.127:10801',
'sslProxy': '10.179.70.127:10801',
"autodetect": 'false'
}
} |
@gregjacobs I need to specify a username/password for our proxy used on the |
@luker2 Unfortunately I'm not exactly sure, but does |
@gregjacobs yes, I hadn't followed up yet but that's what ended up working! For others, I also had to url encode the username:password part to escape special characters...
|
@luker2 Awesome, glad to hear you got it working! And thanks for posting that piece about uri encoding the username and password - good catch! |
No description provided.
The text was updated successfully, but these errors were encountered: