Http3

Fixed

* Fixed `response.elapsed` property. (Pull 1313)
* Fixed client authentication interaction with `.stream()`. (Pull 1312)

Fixed

* ASGITransport now properly applies URL decoding to the `path` component, as-per the ASGI spec. (Pull 1307)

Added

* Added support for curio. (Pull https://github.com/encode/httpcore/pull/168)
* Added support for event hooks. (Pull 1246)
* Added support for authentication flows which require either sync or async I/O. (Pull 1217)
* Added support for monitoring download progress with `response.num_bytes_downloaded`. (Pull 1268)
* Added `Request(content=...)` for byte content, instead of overloading `Request(data=...)` (Pull 1266)
* Added support for all URL components as parameter names when using `url.copy_with(...)`. (Pull 1285)
* Neater split between automatically populated headers on `Request` instances, vs default `client.headers`. (Pull 1248)
* Unclosed `AsyncClient` instances will now raise warnings if garbage collected. (Pull 1197)
* Support `Response(content=..., text=..., html=..., json=...)` for creating usable response instances in code. (Pull 1265, 1297)
* Support instantiating requests from the low-level transport API. (Pull 1293)
* Raise errors on invalid URL types. (Pull 1259)

Changed

* Cleaned up expected behaviour for URL escaping. `url.path` is now URL escaped. (Pull 1285)
* Cleaned up expected behaviour for bytes vs str in URL components. `url.userinfo` and `url.query` are not URL escaped, and so return bytes. (Pull 1285)
* Drop `url.authority` property in favour of `url.netloc`, since "authority" was semantically incorrect. (Pull 1285)
* Drop `url.full_path` property in favour of `url.raw_path`, for better consistency with other parts of the API. (Pull 1285)
* No longer use the `chardet` library for auto-detecting charsets, instead defaulting to a simpler approach when no charset is specified. (1269)

Fixed

* Swapped ordering of redirects and authentication flow. (Pull 1267)
* `.netrc` lookups should use host, not host+port. (Pull 1298)

Removed

* The `URLLib3Transport` class no longer exists. We've published it instead as an example of [a custom transport class](https://gist.github.com/florimondmanca/d56764d78d748eb9f73165da388e546e). (Pull #1182)
* Drop `request.timer` attribute, which was being used internally to set `response.elapsed`. (Pull 1249)
* Drop `response.decoder` attribute, which was being used internally. (Pull 1276)
* `Request.prepare()` is now a private method. (Pull 1284)

Added

* `http.Response()` may now be instantiated without a `request=...` parameter. Useful for some unit testing cases. (Pull 1238)
* Add `103 Early Hints` and `425 Too Early` status codes. (Pull 1244)

Fixed

* `DigestAuth` now handles responses that include multiple 'WWW-Authenticate' headers. (Pull 1240)
* Call into transport `__enter__`/`__exit__` or `__aenter__`/`__aexit__` when client is used in a context manager style. (Pull 1218)

Added

* Support `client.get(..., auth=None)` to bypass the default authentication on a clients. (Pull 1115)
* Support `client.auth = ...` property setter. (Pull 1185)
* Support `httpx.get(..., proxies=...)` on top-level request functions. (Pull 1198)
* Display instances with nicer import styles. (Eg. <httpx.ReadTimeout ...>) (Pull 1155)
* Support `cookies=[(key, value)]` list-of-two-tuples style usage. (Pull 1211)

Fixed

* Ensure that automatically included headers on a request may be modified. (Pull 1205)
* Allow explicit `Content-Length` header on streaming requests. (Pull 1170)
* Handle URL quoted usernames and passwords properly. (Pull 1159)
* Use more consistent default for `HEAD` requests, setting `allow_redirects=True`. (Pull 1183)
* If a transport error occurs while streaming the response, raise an `httpx` exception, not the underlying `httpcore` exception. (Pull 1190)
* Include the underlying `httpcore` traceback, when transport exceptions occur. (Pull 1199)

Added

* The `httpx.URL(...)` class now raises `httpx.InvalidURL` on invalid URLs, rather than exposing the underlying `rfc3986` exception. If a redirect response includes an invalid 'Location' header, then a `RemoteProtocolError` exception is raised, which will be associated with the request that caused it. (Pull 1163)

Fixed

* Handling multiple `Set-Cookie` headers became broken in the 0.14.0 release, and is now resolved. (Pull 1156)