wasn't updating length, which made queries for #empty? return true
in cases where it shouldn't. this fix circumvents that by nullifying
inflaters, thereby ensuring that the default behaviour matches the mock
reality.

Closes #372

webmock: remove override of #decode_chunk

Closes #372

See merge request !432

this allows the rate_limiter plugin to override the method without patching the option and potentially overriding a client value

retries: moved extraction of retry_after interval to internal method

See merge request !434

Fix the command in test docs

See merge request !436

the IOError exception will get a specific overridable handling function
(which by default will do the same as the general one).

there may be requests in the pending queue

considering that these will get rerouted

the connection close flow was doing the following in order:

* purge (cleaning buffers, closing socket)
* disconnecting (which checks the connection back in)
* setting the state to :closed

the last 2 steps are the race condition, as after connection is checked
in, the context may be switched **before** the state is `:closed`; and
then context may be switched back to it and state will be set to
`:closed` when it should not, leaving the connection in a corrupt state.

the problem is exacerbated for persistent connections, which may be
checked out from the pool in a state other than inactive.

this fixes it by adding the concept of a post state transition internal
callback, so in the case of both `:inactive` and `:closed` transitions,
disconnection only happens after the state has been set.

also, scoping logs to session instead of connection.

not all IOs can be nonblocking, like stdout; also, fix tries counter by excluding reentrant resolve calls where a query may already be undergoing

chore: add specific io error callback

See merge request !437

specially for WINDOW_UPDATE, where current state of remote/local window
is now logged to bookkeep flow control accounting.

this will verify that, at this point, httpx continues to before request
data, despite the server already replying with a response and
half-closing the stream.

the connection may have had buffered data waiting for WINDOW_UPDATE
increments, and those may still be buffered after the peer closes their
end of the stream. this effectively nullifies that, while also send a
last data frame closing the client end of the stream.

on stream half-close, thrash buffered data on the parser

See merge request !433

Alexander Mankuta authored Feb 17, 2026 and Tiago committed Mar 05, 2026

The API follows Array API.

- `delete` allows deletion if individual cookies. These cookies have to
  be instances of Cookie class. The can be either previously manually
  created and added to the jar cookies, or cookies found in the jar.
- `reject!`/`delete_if` allows deletion with a block.
- `select!`/`filter!`/`keep_if` allows keeping only specific cookies,
  selected by the block, and removal of the rest.
- `clear` allows removal of all cookies, it also can remove cookies
  that would match a URI (similar to how `[]` selects cookies)

It should implement the following methods from CookieStore:

* #get(name_or_options) -> returns the first matched cookie
* #get_all(name_or_options) -> returns array of cookies
* #set(name_or_options, value_if_name)
* #delete(name_or_options)

this should simplify the task of creating a jar object to be manipulated
directly by the end user.

cookies plugin: CookieStore API

Closes #374

See merge request !435