Skip to content

Releases: jawah/urllib3.future

Version 2.5.904

21 Feb 05:30
1378e51
Compare
Choose a tag to compare

2.5.904 (2024-02-21)

  • Improved reliability with PoliceTraffic.borrow with type as indicator when heavily accessed by many threads.

Version 2.5.903

20 Feb 06:37
8c6ff60
Compare
Choose a tag to compare

2.5.903 (2024-02-20)

  • Fixed an edge case where a simultaneous call to get_response() without a specific promise could lead to a non-thread safe operation.

Version 2.5.902

04 Feb 18:28
b7043a1
Compare
Choose a tag to compare

2.5.902 (2024-02-04)

  • Fixed missed clean-up of unused PoolKey stored in PoliceTraffic upon a full PoolManager.

Version 2.5.901

02 Feb 18:14
589466f
Compare
Choose a tag to compare

2.5.901 (2024-02-02)

  • Fixed a compatibility issue with boto3 when trying to send data (got an unexpected keyword argument). #79

Version 2.5.900

02 Feb 05:17
e3522e5
Compare
Choose a tag to compare

2.5.900 (2024-02-02)

  • Improved performance and reliability for concurrent streams handled by a single connection.
    We relied on a flat array of events generated by the protocol state-machine that unfortunately was not
    efficient. urllib3-future now handle the events with a matrix/multi-dimensional array bound to time.
  • Fixed a thread safety issue when a single multiplexed connection was used across many threads.
    We revised in-depth the logic wrapper around the connection locking to make sure you may
    go all-in when using threads in that particular context. In consequence to that:
    1. We are, effective immediately, deprecating RecentlyUsedContainer
      in favor of our internal PoliceTraffic that was used in PoolManager.
    2. No longer using Queue to manage the Connection in HTTPConnectionPool.
      If you try to set HTTPConnectionPool.QueueCls it will raise a deprecation warning.
      Starting today, we no longer accept implementation like queue.Queue because it
      cannot fit the need of this complex HTTP client, especially with the multiplexing aspect.
  • Increased default pool maxsize for DNS-over-HTTPS from 1 to 10.

Version 2.4.906

19 Jan 05:58
2f34e63
Compare
Choose a tag to compare

2.4.906 (2024-01-19)

  • Fixed a rare case of HTTP/3 being disabled when forwarding a custom SSLContext created.
  • Re-introduce DEFAULT_CIPHERS constant in urllib3.util.ssl_ due to the demands.
    It contains the Mozilla recommended cipher suite that was introduced in version 2.2.900.
  • Fixed handling of OpenSSL 3.2.0 new error message for misconfiguring an HTTP proxy as HTTPS.
    Ported from urllib3/3271.
  • Fixed request_sent_latency that wasn't computed when request was stopped early (prior to sending the
    complete body).

Version 2.4.905

16 Jan 14:47
40f52e6
Compare
Choose a tag to compare

2.4.905 (2024-01-16)

  • Fixed an edge case where a HTTPS record was misinterpreted when using a DNS-over-HTTPS resolver.

Version 2.4.904

15 Jan 07:20
1d92d54
Compare
Choose a tag to compare

2.4.904 (2024-01-15)

  • Fixed an issue where a idle QUIC connection would not be recycled properly when expired.
  • Added support for passing -1 as the amt in HTTPResponse (read, or stream) as the strict equivalent of read1.
    This allows you to fetch content as soon as it arrive.
  • Removed orphaned method _handle_chunk, _update_chunk_length from HTTPResponse.
  • Fixed the iterator in HTTPResponse that hung until the complete content was downloaded.

Version 2.4.903

07 Jan 21:10
Compare
Choose a tag to compare

2.4.903 (2024-01-07)

  • Fixed an issue where setting None for a header value could cause an exception.

Version 2.4.902

01 Jan 03:46
72da7f7
Compare
Choose a tag to compare

2.4.902 (2024-01-01)

  • Fixed compatibility with older PyPy 3.7 interpreters when HTTP/3 (qh3) can be unavailable.
  • Fixed undesired DGRAM/QUIC preemptive upgrade using insecure protocol.