On Sun, 10 Jan 2021, Midnight Wonderer wrote:
Thanks for explaining!
This is potentially affecting most HTTP-based services in existence.
But client retry is not practical, mostly because there is no standard for
it. Some clients took, like, a minute to try the next IP address. Take curl
as an example, which goes the way it is.
I wouldn't mind tweaking the default algorithm/timeout handling. libcurl
currently uses a 300 second timeout for connecting by default, which is
ridiculously long.
If the feature is there, I can tell our client to utilize it for a better
chance of serviceability.
Okay, I think understand you better now.
So what would your ideal solution to this in libcurl look like?
--
/ daniel.haxx.se
| Commercial curl support up to 24x7 is available!
| Private help, bug fixes, support, ports, new features
| https://www.wolfssl.com/contact/
-------------------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette: https://curl.se/mail/etiquette.html
