ferrijs-fetch 0.2.3

A WHATWG Fetch model and one send engine over reqwest: manual redirects, a cookie bridge, multipart, and the SSRF guard the ferrijs sandbox enforces per hop.
Documentation

A spec-faithful WHATWG Fetch model and the single send engine over reqwest. A JS fetch global and a host's own HTTP client API both marshal into the same [Request], go through the same [send] path, and read back the same [Response] — there is no second code path.

Layout:

  • [headers] — the WHATWG header list.
  • [body] — request/response body (Empty / Bytes / stream).
  • [model] — [Request] / [Response] + the RedirectMode / Credentials / ResponseType enums and RemoteAddr.
  • [error] — the typed [FetchError].
  • [engine] — the client pool and the one manual-redirect send loop.
  • [net_guard] — SSRF policy (allow-list, metadata/private blocking).
  • [cookie] — RFC 6265 parsing/matching for the context-bound path.
  • [multipart] — multipart/form-data serialization and parsing.
  • [bridge] — the two-way cookie/defaults bridge to a host-owned jar (a browser context, a session store).
  • [cookie] also carries the [Cookie] record that bridge speaks.