You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
from the user: "it looks like it fails with a couple timeouts, which is usually what happens when something tries to go outbound on 443 and the router blocks it."
The text was updated successfully, but these errors were encountered:
Further background, the most common way to configure the http(s) proxy is through environment variables: http_proxy, https_proxy, no_proxy, or their uppercase variants.
This appears to be the function in question. Since you're using hyper directly, instead of reqwest or ureq or some other http client library that already supports proxies, it might mean a bit more work for us. I think maybe the best route would be to try and lift the proxy logic from reqwest if possible. I'm pretty sure it also uses hyper.
Headers are based on how `curl` and env variables on`reqwest`.
Setting any of
- `HTTP_PROXY`
- `http_proxy`
- `HTTPS_PROXY`
- `https_proxy`
will make all relay code use these to proxy outgoing connections.
Closes#2295
## Breaking Changes
- Added `iroh_net::endpoint::Builder::proxy_url`
- Added `iroh_net::endpoint::Builder::proxy_from_env`
- Added `iroh_net::relay::http::ClientError::Proxy` enum variant
## TODOs
- [x] config & parsing env variables
- [x] the todos in the code
- [x] https proxy
- [x] testing: tested manually on two machines using `squid`
reqwest
doThe text was updated successfully, but these errors were encountered: