-
-
Notifications
You must be signed in to change notification settings - Fork 10.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Happy Eyeballs with Axios? #4534
Comments
Hello! 👋 This issue is being automatically closed because it does not follow the issue template. Please read the issue template carefully and follow all of the instructions when opening a new issue. Thanks |
Hi, There is no support for this, however if you want to give it a shot please open a pull request and tag me to review it. Thanks |
I am going to try to add this feature unless someone else is already working on this. |
@rpassmore01 Have you made any progress? |
Sorry I forgot to follow up with this one. I did quite a bit of work trying to get this working, but realized during testing that the HTTP library's request does in fact check other addresses including ipv4 and ipv6. I'm pretty sure that the HTTP library does not use the happy eyeballs algorithm under the hood, so this could still be implemented into Axios. However, it seemed redundant to me since all IPv4 and IPv6 addresses are checked anyways. |
@josedgm (tracking the rest upstream seems like a solid choice) |
Hi
Is there a way to implement something like Happy Eyeballs (RFC 8305) in Axios?
This means that if a hostname has several A records in its DNS answer, Axios must continue trying IP after IP until one gets a proper reply.
Currently, Axios only uses the 1st IP from the DNS reply. Is there a way to force it to continue trying other IPs if the first one is not responsive?
Thanks
The text was updated successfully, but these errors were encountered: