urllib3 is an amazing tool and I'm glad so many "higher level" HTTP clients are not trying to reinvent the wheel but sit on top of it, as HTTP 1/2/3 are complicated protocols :D
Great that you default to TLS 1.2, I see many browsers are nuking TLS 1.0 and 1.1 as well.
I definitely didn't know about the existence of Zstandard, very interesting.
I have a question: do you and the team have plans to start looking into QUIC/HTTP3 or is it too early to consider?
I've worked with Jeremy Laine and helped shape the aioquic library into a state that can be used for sync and async libraries.
For urllib3 we'll not be moving off of httplib's HTTP parser so that makes switching to another protocol above HTTP/1.1 pretty much impossible. Who knows what the future holds though! :)
Hi Seth, thanks a lot for the updates!
urllib3is an amazing tool and I'm glad so many "higher level" HTTP clients are not trying to reinvent the wheel but sit on top of it, as HTTP 1/2/3 are complicated protocols :DGreat that you default to TLS 1.2, I see many browsers are nuking TLS 1.0 and 1.1 as well.
I definitely didn't know about the existence of Zstandard, very interesting.
I have a question: do you and the team have plans to start looking into QUIC/HTTP3 or is it too early to consider?
I've worked with Jeremy Laine and helped shape the aioquic library into a state that can be used for sync and async libraries.
For urllib3 we'll not be moving off of httplib's HTTP parser so that makes switching to another protocol above HTTP/1.1 pretty much impossible. Who knows what the future holds though! :)
Thanks for your interest.
Didn't know about aioquic, definitely interesting.
Thanks for the reply and keep up the great work!