HTTP proxy authentication
See original GitHub issueHTTP proxy support was added in #366, but the proxy configuration only takes into account the proxy host and port. We are running in an environment that requires authenticating to the proxy, and as far as I understood, axios doesn’t support that. We are using the standard http_proxy
and https_proxy
environment variables with the credentials in the URL, like http://proxy-user:proxy-password@proxy-host:proxy-port
, and passing that works as expected with e.g. superagent-proxy.
So I’m requesting to have support for HTTP proxy authentication, preferably even taking the credentials automatically from HTTP proxy environment variables.
Issue Analytics
- State:
- Created 7 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Proxy-Authenticate - HTTP - MDN Web Docs
The HTTP Proxy-Authenticate response header defines the authentication method that should be used to gain access to a resource behind a ...
Read more >6.7. Proxy Authentication - HTTP: The Definitive Guide [Book]
Proxy Authentication Proxies can serve as access-control devices. HTTP defines a mechanism called proxy authentication that blocks requests for content ...
Read more >How to pass proxy authentication credentials for HTTP(S ...
How do I enter proxy credentials for HTTP(S) monitor? A: If you use 4.0.9306 or newer release of IPHost Network Monitor, then there...
Read more >HTTP Spec: Proxy-Authorization and Authorization headers
The user makes an HTTP request to the proxy without any sort of authentication. · The proxy answers 407 Proxy Authentication Required and...
Read more >Proxy-Authenticate HTTP RequestHeader: Syntax, Directive ...
Proxy -Authenticate HTTP Request Header provides credentials for auditing in order to support proxy server verification.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thanks a bunch @peruukki !
Weird yeah I’ve just been using request-native-promise instead 🤷♂️
I see why one should normally not set env vars after script starts but I wrote a CLI program that optionally let’s the user configure proxy settings for the rest of the lifetime of the script
The root problem here tho was version of library I was using, setting env vars after script starts was just accidental red herring
Thank u!!
According to the changelog, the fix was included in v0.15.3. Though it still wouldn’t work in our environment and I couldn’t figure out why in a reasonable time, so we kept using superagent instead. 🤷♂️
I’ve always seen environment variables being set before/when the application starts, I’m not sure if it’s possible to set them afterwards (and it doesn’t sound like a good idea anyway).