Urllib3-future

====================

- Added public `ConnectionInfo` class that will be present in each `HttpConnection` instance.

Passing the kwarg ``on_post_connection`` that accept a callable with a single positional argument
in ``PoolManager.urlopen`` method will result in a call each time a connection is picked out
of the pool. The function will be passed a ``ConnectionInfo`` object.
The same argument (``on_post_connection``) can be passed down to the ``HTTPConnectionPool.urlopen`` method. (`23 <https://github.com/jawah/urllib3.future/issues/23>`__)

- `22 <https://github.com/jawah/urllib3.future/issues/22>`__

====================

- Fixed ``HTTPSConnectionPool`` not accepting and forwarding ``ca_cert_data``. (`20 <https://github.com/jawah/urllib3.future/issues/20>`__)

====================

- Fixed `assert_hostname` behavior when HTTPSConnection targets HTTP/3 over QUIC (`8 <https://github.com/jawah/urllib3.future/issues/8>`__)
- Fixed protocol violation for HTTP/2 and HTTP/3 where we sent ``Connection: keep-alive`` when it is
forbidden. (`16 <https://github.com/jawah/urllib3.future/issues/16>`__)
- Fixed ``unpack_chunk`` workaround function in the ``send`` method when body is multipart/form-data (`17 <https://github.com/jawah/urllib3.future/issues/17>`__)
- Fixed the flow control when sending a body for a HTTP/2 connection.
The body will be split into numerous chunks if the size exceed the specified blocksize when not
using HTTP/1.1 in order to avoid ProtocolError (flow control) (`18 <https://github.com/jawah/urllib3.future/issues/18>`__)

====================

Features
--------

- Added experimental support for HTTP/1.1, HTTP/2 and HTTP/3 independently of httplib.

Currently urllib3 does not offer async http request and the backend is the http.client package
shipped alongside Python. This implementation is not scheduled to improve, even less to support latest
protocol.

Without proxies, the negotiation is as follow:

- http requests are always made using HTTP/1.1.
- https requests are made with HTTP/2 if TLS-ALPN yield its support otherwise HTTP/1.1.

- https requests may upgrade to HTTP/3 if latest response contain a valid Alt-Svc header.

With proxies:

- The initial proxy request is always issued using HTTP/1.1 regardless if its http or https.
- Subsequents requests follow the previous section (Without proxies) at the sole exception that HTTP/3 upgrade is disabled.

You may explicitly disable HTTP/2 or, and, HTTP/3 by passing ``disabled_svn={HttpVersion.h2}`` to your ``BaseHttpConnection`` instance.
Disabling HTTP/1.1 is forbidden and raise an error.

Note that a valid or accepted Alt-Svc header in urllib3 means looking for the "h3" (final specification) protocol and disallow switching hostname for security
reasons. (`1 <https://github.com/jawah/urllib3.future/issues/1>`__)
- Added ``BaseHTTPResponse`` to ``__all__`` in ``__init__.py`` (`3078 <https://github.com/urllib3/urllib3/issues/3078>`__)

==================

- Allowed alternative SSL libraries such as LibreSSL, while still issuing a warning as we cannot help users facing issues with implementations other than OpenSSL. (`3020 <https://github.com/urllib3/urllib3/issues/3020>`__)
- Deprecated URLs which don't have an explicit scheme (`2950 <https://github.com/urllib3/urllib3/pull/2950>`_)
- Fixed response decoding with Zstandard when compressed data is made of several frames. (`3008 <https://github.com/urllib3/urllib3/issues/3008>`__)
- Fixed ``assert_hostname=False`` to correctly skip hostname check. (`3051 <https://github.com/urllib3/urllib3/issues/3051>`__)

==================

- Fixed ``HTTPResponse.stream()`` to continue yielding bytes if buffered decompressed data
was still available to be read even if the underlying socket is closed. This prevents
a compressed response from being truncated. (`3009 <https://github.com/urllib3/urllib3/issues/3009>`__)