Expand description
HTTP/1.1 data transport.
NOTE: Transport is deep configuration of ureq and is not required for regular use.
ureq provides a pluggable transport layer making it possible to write bespoke
transports using the HTTP/1.1 protocol from point A to B. The
Agent::with_parts() constructor takes an implementation
of the Connector trait which is used for all connections made using that
agent.
The DefaultConnector covers the regular needs for HTTP/1.1:
- TCP Sockets
- SOCKS-proxy sockets
- HTTPS/TLS using rustls (feature flag rustls)
- HTTPS/TLS using native-tls (feature flag native-tls + config)
The Connector trait anticipates a chain of connectors that each decide
whether to help perform the connection or not. It is for instance possible to make a
connector handling other schemes than http/https without affecting “regular” connections
using these schemes. See ChainedConnector for a helper connector that aids setting
up a chain of concrete connectors.
Modules§
- Internal time wrappers
Structs§
- Helper for a chain of connectors.
- Connector for CONNECT proxy settings.
- The parameters needed to create a
Transport. - Default connector providing TCP sockets, TLS and SOCKS proxy.
- Default buffer implementation.
- Connector for SOCKS proxies.
- Connector for regular TCP sockets.
Traits§
- Abstraction over input/output buffers.
- Trait for components providing some aspect of connecting.
- Transport of HTTP/1.1 as created by a
Connector.
Functions§
- Helper for _test feature tests.