The description of --anyauth says
Tells curl to figure out authentication method by itself, and use the most secure one the remote site claims
to support. This is done by first doing a request and checking the response-headers, thus possibly inducing an
extra network round-trip.
It works by sending the request with ...
2 solutions to this :
you can create a shell alias such as : alias curl='curl --proxy http://[host]:[port]'
or define the proxy settings in a cURL config file : echo 'proxy = [host]:[port]' > ~/.curlrc
I've not been able to make this work using environment variables.
NB : your configuration defines HTTPS_PROXY and HTTP_PROXY both as uppercase and ...
locate is not "real time" : it scans the filesystem and remembers files and locations in its internal database.
This is what's happening to you here when running :
You're served the outdated value of this file's location because the database has not (yet) been updated.
You can force this with :
full details : https://ss64....
It seems that github.com is not behaving politely by saying that the resource does not exist when a non-authenticated GET request is made. Normally wget will first try requesting the resource without authentication, and retry with that authentication data when a 401 Not Authenticated error is given.
This can be worked around by passing --auth-no-challenge ...