Nice seeing support of modern protocols in http libraries

That's pretty bold claims

Looks cool! Will have to give it a try to see if it works like promised!

will be glad to answer any concerns if you encounter any, the repo issue tracker will welcome your feedbacks.

Does it support happy eyeball algorithm for dual stack and portions of it for single stack, when multiple A(dress) records are returned, to figure out which destination accepts our connect() ?

Not yet, but is coming soon. We have a minor technical challenge to make it work with QUIC.

That would be awesome if even just for tcp protocols.

I've been looking at contrib.resolver in urllib3.future and noticed that you only parse A,AAAA,HTTPS from responses, but you do not handle a CNAME. I wonder, because kubernetes service can return a CNAME for app to follow:

https://kubernetes.io/docs/concepts/services-networking/serv...

Just wonder, if this is something worth pursuing, to follow one CNAME...

I'm fully aware this is not a recursive resolver, but just wondering about a CNAME response from coredns here...

This would be done gladly. Open an issue at urllib3.future and a proper tracking will be made.

The internal resolver is recursive, so CNAME are automatically translated into addresses. What remain is the happy eyeball implementation, which is almost completed already. we wanted to wait for an harmonious feature (e.g. available across all 3 protocols)

but can be speeded up if really needed.

there https://github.com/jawah/urllib3.future/issues

TIL requests is still at HTTP/1.1 by default. That's... Internet Explorer old.

Wow, that feature matrix is some A++ - it makes me want to try and integrate this into Scrapy to make its requests stand out less, extra bonus if niquests allows fine-grain control over header ordering and similar fingerprint-avoidance trickery

Glad to hear that. This is actually planned, the miscellaneous control for networking fingerprint (mimic chrome tls handshake). will come soon enough. for now, my own experience shows that it is more resilient as is (with appropriate headers (order being kept already).