Re: [Libguestfs] [PATCH nbdkit] curl: Add effective-url flag

Personally I think the calling application knows how to handle certain scenarios well enough, that it should figure out the effective URL ahead of time. But I believe the objection from my colleagues is that it is using a hammer to solve the problem. nbdkit knows the internals of nbdkit, and it could come up with a more effective mechanism to deal with these mirror failures. Is it possible to do a retry on the byte range level? Basically if a particular range fails, retry it and possibly get a new mirror that does work, instead of failing the entire import at that point.

I can't think of any other way to solve this in the context of nbdkit (maybe have it detect when redirection is happening and retry the redirection on error?).