Struct ConnectionDetails

pub struct ConnectionDetails<'a> {
    pub uri: &'a Uri,
    pub addrs: ArrayVec<SocketAddr, ureq::::unversioned::resolver::ResolvedSocketAddrs::{constant#0}>,
    pub config: &'a Config,
    pub request_level: bool,
    pub resolver: &'a (dyn Resolver + 'static),
    pub now: Instant,
    pub timeout: NextTimeout,
    pub proxied: Option<&'a Uri>,
}

Available on crate feature dep_ureq only.

The parameters needed to create a Transport.

Fields

uri: &'a Uri

Full uri that is being requested.

In the case of CONNECT (HTTP) proxy, this is the URI of the proxy, and the actual URI is in the proxied field.

addrs: ArrayVec<SocketAddr, ureq::::unversioned::resolver::ResolvedSocketAddrs::{constant#0}>

The resolved IP address + port for the uri being requested. See Resolver.

For CONNECT proxy, this is the address of the proxy server.

config: &'a Config

The configuration.

Agent or Request level.

request_level: bool

Whether the config is request level.

resolver: &'a (dyn Resolver + 'static)

The resolver configured on Agent.

Typically the IP address of the host in the uri is already resolved to the addr property. However there might be cases where additional DNS lookups need to be made in the connector itself, such as resolving a SOCKS proxy server.

now: Instant

Current time.

timeout: NextTimeout

The next timeout for making the connection.

proxied: Option<&'a Uri>

In case of CONNECT (HTTP) proxy, this is the actual requested uri that will go through the proxy.

This ends up in the connect line like CONNECT host:port HTTP/1.1.

For socks proxy it is None.

Implementations

impl<'a> ConnectionDetails<'a>

pub fn needs_tls(&self) -> bool

Tell if the requested socket need TLS wrapping.

This is (obviously) true for URLs starting https, but also in the case of using a CONNECT proxy over https.