HTTP Accept-Encoding algorithms the client advertises and is
willing to decode. Reqwest auto-adds the corresponding
Accept-Encoding header for every algorithm whose flag is set;
the rest are disabled via ClientBuilder::no_* so the wire
header stays in lockstep with this set.
Production HTTP client used across the workspace. Wraps a raw
Client with the workspace’s [RetryNet] decorator so
every Net method (head/get_bytes/post_bytes/get_range/stream) honours
options.retry_policy — retryable errors (TLS-close, timeout,
5xx, IO) are re-issued with exponential backoff; non-retryable
errors (HTTP 4xx, cancellation) propagate immediately.
TLS+HTTP fingerprint the native client-wreq backend impersonates. The
DRM keyserver sits behind an anti-bot WAF that fingerprints the TLS
ClientHello (JA3) and 418-rejects non-browser stacks; presenting a real
browser fingerprint via wreq is what gets a 200. Default Safari matches
iOS URLSession; Android selects a different preset. Inert under the
client-reqwest backend and on wasm32 (no emulation; the browser fetch
already carries a real fingerprint).