Tags: jawah/urllib3.future
Tags
Release 2.12.917 (#226) 2.12.917 (2024-04-10) ===================== - Improve keepalive handling for connections. We now listen for an incoming pong frame after emitting a ping frame. Moreover we ensure better strictness around set ``keepalive_delay`` and consider every connection dropped after set delay. (Close jawah/niquests#240)
Release 2.12.914 (#219) 2.12.914 (2024-03-30) ===================== - Fixed a rare thread safety issue when the size of PoolManager is inferior to the thread count. An edge case permitted the creation of two ``ConnectionPool`` for the same ``PoolKey``. - Changed the default behavior of threads management to not raise an exception if the thread count is greater than the pool size. Making it that way better align with upstream, our initial decision revealed itself to cause confusions for some of our users. No longer will urllib3-future raise ``OverwhelmedTraffic`` in default configuration. - Fixed an error when ``happy_eyeballs=True`` is set with more tasks or threads than the pool size.
Release 2.12.913 (#218) 2.12.913 (2024-03-21) ===================== - Added useful repr for ``PoolManager``, ``ConnectionPool`` and ``TrafficPolice`` (async counterpart included). - Fixed ``KeyError`` upon parsing X509 certificate pulled from the QUIC layer when the certificate contain an unexpected rfc4514 attribute. (#217)
Release 2.12.912 (#214) 2.12.912 (2024-02-07) ===================== - Automatically grab ``qh3`` for HTTP/3 support with PyPy 3.11 - Fixed error while attempting to close a broken ``HTTPResponse`` starting from Python 3.14 If the Content-Type is invalid or malformed, the constructor stopped initializing some members that are required in the closing procedure. (e.g. using ctx) - Fixed an error when libffi does not support in-memory I/O handler. Seen so far with PyPy 3.11 beta.
Release 2.12.909 (#204) 2.12.909 (2024-01-20) ===================== - Fixed compatibility with upstream urllib3 when third party program invoke deprecated ``HTTPResponse.getheader`` or ``HTTPResponse.getheaders``. Those methods were planned to be removed in 2.1 (they still have a pending deprecation that mention 2.1 target in the 2.3 version). As such we immediately restore the methods. (#203) - Implemented our copy of ``HTTPResponse.read1`` heavily simplified as we do already support ``HTTPResponse.read(-1)``. Also mirrored in ``AsyncHTTPResponse.read1``. - Automatically grab ``qh3`` for X86 based processors (e.g. win32). - Fixed the aggressive exception in our native websocket implementation when a server responded positively to an upgrade request without the required http header. Instead of ``RuntimeError``, now raises ``ProtocolError``.