-
Notifications
You must be signed in to change notification settings - Fork 59
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 support #81
Comments
Hi @ArthurZob Thanks for reporting. Unfortunately, the extension doesn't support work behind a proxy. Probably could be added in the future. |
Hello @SqrTT, |
Hello @SqrTT, Could you tell me if the extension works now behind a proxy ? :) |
Hi @pierreantoinelefebvrepf If you have time/resources I would be glad to merge your PR with the feature. |
@pierreantoinelefebvrepf have you tried setting HTTPS_PROXY env variable? At least for the upload piece the npm request module is used by the extension which claims to respect those: https://www.npmjs.com/package/request#controlling-proxy-behaviour-using-environment-variables |
@pierreantoinelefebvrepf or @ArthurZob did you have a chance to try the above? |
The solution suggested by @SGD1953 works. Adding the proxy configuration to npm makes Prophet Debugger work behind a corporate proxy. More info about configuring npm to work behind a proxy here: https://stackoverflow.com/questions/25660936/using-npm-behind-corporate-proxy-pac |
Hello,
I am not able to upload throught my company proxy. I got this error :
Unable validate connection! Validation error: tunneling socket could not be established, statusCode=504 Error: Error: tunneling socket could not be established, statusCode=504
I can't find anything related to this. Will it be an evolution ? Or is there an alternative solution ?
Regards,
Arthur
The text was updated successfully, but these errors were encountered: