A simple, pluggable interface for HTTP GETs and range requests.
At the moment, there are three backends that might be available:
- A “null” backend that is always available, but does nothing and always fails.
- A backend based on reqwest.
- A backend based on curl.
The actual backend availability is determined at build time using Cargo features. See the crate README for information about the features and how they interact.
The default backend is intentionally exposed as a concrete type, so that crates relying on this one need not use a lot of dyns and impl Traits. It is intended that the choice of HTTP backend is a build-time one, not a runtime one.
A trait for simple HTTP operations needed by the Tectonic backends.
A trait for reading byte ranges from an HTTP resource.
The range-reader type exposed by the default URL-get backend (for convenience).