-
-
Notifications
You must be signed in to change notification settings - Fork 607
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
proxy option not configured for webpagetest results polling #2071
Comments
Hi @garnaud thanks for creating the issue. Hmm we use https://github.com/marcelduran/webpagetest-api in the backend to connect with the WebPageTest server but I don't see a proxy option in the documentation for that, can you show we where you found it we can look into it? Best |
Hi, I had to investigate code but I hadn't see it was an external library. You can see the executed code here. And the call to the method here: get.call(this, config, pathname, options.proxy, options.agent, function apiCallback(err, data, info) {
... I was lucky that options comes from sitespeed.io configuration element {
"webpagetest":{
"host": "some.webpagetest.com",
"proxy": "http://my.company.proxy:80"
}
} But that work only for the first call to the api. For polling the result test, it doesn't reuse the configuration. I don't know why and I'm a little bit lost in nodejs code :) Do you think I need to open an issue to https://github.com/marcelduran/webpagetest-api ? Best Guillaume |
gasp, an issue since 2014 :( |
@garnaud the webpagetest api is often open for PRs so if you have time and try to fix it I think Marcel can merge it. |
Closing this but if it's fixed in the webpagetest api we can implement it here too. |
Hi,
I would like to use a webpagetest server behind my company proxy but the result polling is blocked.
It seems that the proxy parameter is well configured for the webpagetest server call (I can see the launched job on the server) but not for retrieving the test result.
I use docker image
sitespeedio/sitespeed.io:7.0.1
.My configuration file is:
The stack error:
The text was updated successfully, but these errors were encountered: