-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
Help Wanted: Proxy testing #18103
Comments
I am running on Linux Mint 18.1. And there are 2 proxy (from which I can choose) First (this is a simple one, best case scenario):
Second (this is more official one, and no, there is no user/pass needed):
|
@dfroze What is your second proxy? What technology/protocol does it use? Did you configure your OS with your proxy settings? Can you use Google Chrome, does it work without any configuration? |
@joaomoreno
What technology/protocol does it use?
Did you configure your OS with your proxy settings? Can you use Google Chrome, does it work without any configuration?
|
From @eric-brunel OS : Windows 7 Enterprise 64bits Without providing proxy URL:
Without providing credentials (only proxy server URL)
With Credentials
|
@joaomoreno Tried running your app in my environment. No results after running it for 2 hours. It could be my corporate proxy... |
Hi, On my end, with or without providing proxy URL (I didn't provide credentials).
OS : Windows 7 Enterprise 64bits I didn't try entering credentials, since vscode doesn't encrypt them (like what "nuget" does). So having the proxy credentials stored in clear in vscode is not an option. |
OS : Windows 7 Pro 64bits with Credentials:
|
So far so good, it appears both XHR and Electron are the best, since they benefit from the system's configuration, as expected. Except @dfroze, who seems to not have it working. @dfroze does your system have the @akcorp2003 I've improved the timeout mechanism. Can you try the latest version? |
@joaomoreno I've looked it more in the problem with system proxy, apparently there is a way to set it (other then /etc/environment) that is better. By using the Network interface given by the OS there was a way to set the proxy manually which is different and better then the one set in bash Was expecting that just by providing the $HTTP_PROXY environment variable or the Proxy URL from your proxy test application will be more then enough for the connection. Here is re-test using the Network interface given by the OS on the second proxy (the problematic one).
Edited: Just to make sure there are no room for errors. The Network interface given by the OS i was referring to is the following for Linux Mint: |
@dfroze Great news! |
OS : Windows 7 Enterprise 64bits with Credentials: http://user:[email protected]:port
|
@abargstaedt |
Not yet but here it is w/o putting the proxy
|
And here with proxy set but w/o credentials
|
Please don't hesitate to let me know if I can do anything more to help you. I appreciate your great work! |
@abargstaedt What is strange about your setup is that the XHR and Electron methods don't work. Can you tell us more about your proxy setup? What technologies does it use? Can you check around Chrome's network settings, and see if it is manually configured? I find it strange that Chrome works, but Code wouldn't. |
I'm running CentOS 7.2, I am in a corporate environment and I know my proxy address. I can browse VS Code extensions but I can't install them. Our Proxy does not require authetication.
|
I have a Windows 7 with Visual Code 1.8.1 which extension functions works with the same proxy setting as my Linux. The following is the output. I also try both 32 bits and 64 bits Windows version, the output is similar.
|
This time I don't comment all the proxy setting in /etc/environment and all the other settings, then reboot the system, the following is the output (I have run the test several time and I find sometimes error will be timeout, and timeout will be error). The proxy is set in test app and there is no environment variable now.
|
Is this how you are configuring your system? http://www.thesysadminhimself.com/2013/08/configuring-web-proxy-on-centos.html |
@joaomoreno Chrome and my other browsers are set up to use an automatic configuration script (proxy.pac). Then it prompts for user name and password (basic authentication). For other applications that require internet access I have to set up the proxy manually. Normally this works with the pattern I probably should also mention that some genius put the character '@' into the proxy password. So we have to work around that by replacing it with In settings.json I removed the credentials from the "http.proxy" value and inserted the following line: |
WHAT?
…On Friday, January 6, 2017, abargstaedt ***@***.***> wrote:
@joaomoreno <https://github.com/joaomoreno> Chrome and my other browser
are set up to use an automatic configuration script (proxy.pac). Then it
prompts for user name and password (basic authentication).
For other applications that require internet access I have to set up the
proxy manually. Normally this works with the pattern
***@***.***:port. That way it works work npm, Bower, Git
and it used to work for VSCode as well but not anymore.
I probably should also mention that some genius put the character '@' into
the proxy password. So we have to work around that by replacing it with
%40 in above mentioned pattern. Still it works for most applications.
In settings.json I removed the credentials from the "http.proxy" value and
inserted the following line:
"http.proxyAuthorization": "Basic sOMeBASE64eNCODEdSTRING="
The base 64 encoded password above is a fake but it is the same header
that we are using for Fiddler.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#18103 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AXjFUGFRKLaYShuZe8XPqb7uxqc_9S6Aks5rPiAegaJpZM4LajsO>
.
|
@R3V07T We are glad that you reacted to the post and pretty sure there a lot of us shocked about it (maybe). But do please right something more useful and more detailed next time 😆 |
I am running Windows 10 Enterprise and I know the proxy address. I can browse VS Code extensions but I can't install them.
|
That's great news that xhr and electron are widely functional. |
Please take a look at my results between Windows and Linux. XHR and Electron both work on Windows (so the extension function works). The really problem is that Windows work and Linux fail with the same proxy configuration. |
@liaoya |
I'm running Windows 10, corporate domain and behind a proxy. I can browse the extensions but I'm having the
|
Mac OSX 10.11.6, behind corporate firewall, network location set to "office" where proxy autodetect configured. All apps works (including updates for vscode itself) except VSCode extensions marketplace.
|
Windows 8, behind corporate firewall, proxy manualy configured. All apps works (including updates for vscode itself) except VSCode extensions marketplace: can´t browse can´t download
|
|
Windows 7, behind corporate proxy, I know my proxy address and have set both http.proxyStrictSSL (as false) and http.proxy.
|
I'm running Windows 7 behind a corporate proxy, and I'm running both VSCode Version 1.9.1 and VSCode Version 1.10.0-insider. I have the http.proxy setting initialized, and also the http.proxyStrictSSL set to false. I am able to browse the extensions no problem, and see their details pages just fine. Whenever I try to install any extensions, though, I consistently get the "end of central directory record signature not found" error. I have run your utility and the following is the output:
|
Running v1.4.13 on vscode 1.9.1 I'm running Windows 7 Entreprise SP1, Chrome and my other browsers are set up to use an automatic configuration script (proxy.pac). Same as #18103 (comment) I can browse VS Code extensions, I can install them, but I've this problem :
|
Hi joaomoreno -- it looks like this thread has been accumulating feedback since Jan 4. Do you have a fix yet? (Still unable to install extensions, already provided the protocol feedback.) Appreciate the work you are doing. |
@joaomoreno told me that he will put it on the dev tasks for march. So you just have to wait for few days/weeks now. This isn't comfortable but it helps if you are really in need of an important plugin. |
You can also try and get off your proxy if you can. Installing extensions still work without the proxy. |
Another workaround behind corporate proxy requiring authentication is to use Cntlm (http://cntlm.sourceforge.net/), Fiddler as proxy for some reason did not work for this purpose. |
Closing this. We're taking the numbers for investigation. |
Here is my results
I can't install extensions because I have a proxy. I have VSCode 1.8.1. |
Firewall functions as the proxy - no configuration possible or required:
|
@joaomoreno I'm running Windows 7 behind a corporate proxy, and I'm running width VSCode Version 1.9.1(before is 1.7 and no problem). I have the http.proxy setting initialized, and also the http.proxyStrictSSL set to false. I am able to browse the extensions no problem, and see their details pages just fine. Whenever I try to install any extensions, though, I consistently get the "end of central directory record signature not found" error. I have run your utility and the following is the output:
|
@angelia-yuqi just update your vscode to the latest version and it will work. You'd probably need to remove the proxy settings too if it doesn't work. |
@fazouane-marouane I has updated vscode to 1.11.2 and the problem is not resolved and the proxy works in other solution. |
Have you tried removing http proxy config from vscode? |
Details about your machine (platform, OS)
|
Hi! If you were pinged to this thread, it's because VS Code needs your help!
Users behind proxies have had a tough time lately, and we want to make sure we fix this. We've created a small app which will test your machine, network and environment to figure out which network stack works best for you.
App Screenshot
How can I help?
We ask you to:
Run Tests
Example reply:
We thank you in advance!
@liaoya, @dfroze, @akcorp2003, @ruslanch, @bruceauyeung, @raphabi, @eric-brunel, @fazouane-marouane, @Msira10, @onybo, @ywmail, @foisonocean, @xuewang, @distums, @NeWbY100, @abargstaedt
The text was updated successfully, but these errors were encountered: