3 ms·

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

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/service/#externalname 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...

noopside 3y ago
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.
- noopside 3y ago
  there https://github.com/jawah/urllib3.future/issues https://github.com/jawah/urllib3.future/issues