A proxy connector for hyper based applications.
use hyper::{Client, Request, Uri};
use hyper::client::HttpConnector;
use futures::{TryFutureExt, TryStreamExt};
use hyper_proxy::{Proxy, ProxyConnector, Intercept};
use headers::Authorization;
use std::error::Error;
#[tokio::main]
async fn main() -> Result<(), Box<dyn Error>> {
let proxy = {
let proxy_uri = "https://my-proxy:8080".parse().unwrap();
let mut proxy = Proxy::new(Intercept::All, proxy_uri);
proxy.set_authorization(Authorization::basic("John Doe", "Agent1234"));
let connector = HttpConnector::new();
let proxy_connector = ProxyConnector::from_proxy(connector, proxy).unwrap();
proxy_connector
};
// Connecting to http will trigger regular GETs and POSTs.
// We need to manually append the relevant headers to the request
let uri: Uri = "https://my-remote-website.com".parse().unwrap();
let mut req = Request::get(uri.clone()).body(hyper::Body::empty()).unwrap();
if let Some(headers) = proxy.http_headers(&uri) {
req.headers_mut().extend(headers.clone().into_iter());
}
let client = Client::builder().build(proxy);
let fut_http = client.request(req)
.and_then(|res| res.into_body().map_ok(|x|x.to_vec()).try_concat())
.map_ok(move |body| ::std::str::from_utf8(&body).unwrap().to_string());
// Connecting to an https uri is straightforward (uses 'CONNECT' method underneath)
let uri = "https://my-remote-websitei-secured.com".parse().unwrap();
let fut_https = client.get(uri)
.and_then(|res| res.into_body().map_ok(|x|x.to_vec()).try_concat())
.map_ok(move |body| ::std::str::from_utf8(&body).unwrap().to_string());
let (http_res, https_res) = futures::future::join(fut_http, fut_https).await;
let (_, _) = (http_res?, https_res?);
Ok(())
}
hyper-proxy
exposes three main Cargo features, to configure which TLS implementation it uses to
connect to a proxy. It can also be configured without TLS support, by compiling without default
features entirely. The supported list of configurations is:
- No TLS support (
default-features = false
) - TLS support via
native-tls
to link against the operating system's native TLS implementation (default) - TLS support via
rustls
(default-features = false, features = ["rustls"]
) - TLS support via
rustls
, using a statically-compiled set of CA certificates to bypass the operating system's default store (default-features = false, features = ["rustls-webpki"]
)
Large part of the code comes from reqwest. The core part as just been extracted and slightly enhanced.
Main changes are:
- support for authentication
- add non secured tunneling
- add the possibility to add additional headers when connecting to the proxy