Closed jecogeo closed 5 years ago
I use yay behind a proxy without any issue. Are you using yay compiled with go or gcc-go?
Also, if it helps, my working proxy is of the type: http_proxy= http://123.456.789.098:465/
with protocol and port specified.
Behind a proxy server it's normal that yay
doesn't work without going through it (if the network is properly setup) so I don't understand what you mean with removing the proxy :confused:
For proxy, yay doesn't change anything except using Go's http library (https://golang.org/pkg/net/http/#ProxyFromEnvironment) so this problem would apply to all your go programs
While writing a reply, I've identified that HTTPS_PROXY (upper case) environment variable is set as /
. Not sure why. Even if http_proxy (lower case) is right, the upper case variable was causing the issue. Correting this and everything is working good. Thanks and sorry for opening this unnecessary issue.
Regards
Affected Version
yay v9.1.0 - libalpm v11.0.3
Issue
yay doesn't work under proxy servers and even removing the proxy from environment variables, it doesn't work as well. The
/etc/sudoers
file already has the lineDefaults env_keep += "ftp_proxy http_proxy https_proxy no_proxy"
.Steps to reproduce
echo $http_proxy
example output:123.456.789.098
export http_proxy=""
echo $http_proxy
the output is a blank line.yay -Syua
Output