Expand description
The one send engine.
A single manual-redirect loop over reqwest handles every request:
fetch global, Playwright request, standalone or context-bound.
reqwest is only the per-hop transport (redirect::Policy::none());
redirect following, cookie bridging, retries, the net-guard per-hop
check, and the timeout budget all live here. Cookies come from the
reqwest jar (standalone) or the browser context (bridged) — the only
difference between the two.
Structs§
- Client
Pool - A cache of
reqwest::Clients that differ only in TLS posture and the DNS-layer guard filter. Every client follows no redirects (the loop does) and shares the pool’s cookie jar, if it has one.