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
NVDA updater and password protected proxies #2950
Comments
Comment 1 by jteh on 2013-01-26 21:22 |
Comment 2 by quetzatl (in reply to comment 1) on 2013-01-28 08:44 There is the end of my log file: Performing automatic update check I think that NVDA should be able to take the username and password, or, instead, should be able to ask these details. Replying to jteh:
|
Comment 3 by jteh on 2013-01-29 01:27 |
Comment 4 by jteh on 2015-01-19 02:44 |
No response to last question and can't contact reporter. Closing. |
Hello. It seems that, in ONCE's case, username and password are stored in Credentials Manager (Windows's Control Panel). I don't have access to this proxy, but contact with the original reporter. Regards. |
With the introduction of NVDA 2019.3, it is possible to connect to this kind of proxies by adding the "HTTP_PROXY" and "HTTPS_PROXY" environment variables to the windows user profile, containing the full Proxy address (e.g. http://me:mypassword@miproxy.micompany.com:3128). this has been tested with ciberpxy.once.org with good results. Regards. |
Reported by quetzatl on 2013-01-26 17:32
NVDA should use the proxy settings configured in the OS to download updates from networks that use these proxies
The text was updated successfully, but these errors were encountered: