refactoring towards not centralizing this inforation

this leaves synchronization out ftm

pools are then used only to fetch new conenctions; selectors are discarded when not needed anymore; HTTPX.wrap is for now patched, but would ideally be done with in the future

allowing it to be plugin extended via pool_class and PoolMethods

also fixed the coalescing case where the connection may come from the pool, and should therefore be remmoved from there and selected/checked back in accordingly as a result

defaulting to unbounded, in order to preserve current behaviour; this will cap the number of connections initiated for a given origin for a pool, which if not shared, will be per-origin; this will include connections from separate option profiles

a pool timeout is defined to checkout a connection when limit is reeached

this eliminates the overuse of Connection#origin, which in the case of proxied connections was broken in the previous commit

the proxy implementation got simpler, despite this large changeset

because you're reconnecting to the same host, now the previous connection is closed, in order to avoid a deadlock on the pool where the per-host conns are exhausted, and the new connection can't be initiated because the older one hasn't been checked back in

instead of fiber-local storage; this allows that under fiber-scheduler based engines, like async, requests on the same session with an open selector will reuse the later, thereby ensuring connection reuse within the same thread

in normal conditions, that'll happen only if the user uses a session object and uses HTTPX::Session#wrap to keep the context open; it'll also work OTTB when using sessions with the  plugin. Otherwise, a new connection will be opened per fiber

but only when the selector is empty, as there'll be nothing to select on, and this would fall into an infinite loop

before, compressed bodies were yielding chunks and buffering locally (the  variant in this snippet); they were also failing to rewind, due to lack of method (fixed in the last commit); in this change, support is added for bodies which can read and rewind (but do not map to a local path via ), such as compressed bodies, which at this point haven't been yet buffered; the procedure is then to buffer the compressed body into a tempfile, calculate the hexdigest then rewind the body and move on

also, error when trying to calculate hexdigest on endless bodies

aws sigv4support calculation of hexdigest on top of compressed bodies in correct way

See merge request !355

Fix incorrect hash key rendering with Oj JSON encoder

Closes #324

See merge request !356

David Roetzel authored Dec 02, 2024 and HoneyryderChuck committed Dec 02, 2024

Closes #323

Add support for `content-digest` headers (RFC9530)

See merge request !354

content-digest: set validate_content_digest default to false; do not try to compute content-digest for requests with no body

:pool option + thread-safe session-owned conn pool

See merge request !348

sarna authored Dec 03, 2024 and HoneyryderChuck committed Dec 03, 2024

Fixes #326 #327

Accept more MIME types with json suffix

Closes #326

See merge request !357

this is a regression from a ractor compatibility commit, which ensured that errors raised while preparing the request / resolving name are caught and raised, but introduced a regression when name resolution retrieves a cached IP; this error only manifested in dual-stack situations, which can't be tested in CI yet

Closes #329

includes nokogiri type sigs

XML plugin

Closes #325

See merge request !358