[ Moving the discussion to the Wget mailing list. Jerry's patch implements a "--random" option that shuffles the list of addresses returned by getaddrinfo. ]
Jerry Lundström <[EMAIL PROTECTED]> writes: > A user scenario could be that wget with ipv6 enabled always picks a > broken website since RFC 3484 deside that it should sort IPs in the way > it does. Not really -- Wget (stably) sorts the address list to prefer IPv4 addresses. This can be influenced using the --prefer-family option. Even if that were the case, Wget should be perfectly able to connect to the next host in the address list, so the error would be non-fatal, only incurring a small delay. > It is fatal to automated script to always pick the broken mirror. It is wrong to fix this by: a) introducing randomness, b) requiring user intervention (how many users will even be aware of this option?), and c) *still* allowing the broken mirror to be chosen by the said randomness if the user is unlucky. > Also, as mirror manager you might get 1/2 overloaded servers since > the sort function is the way it is. I don't think Wget is the most popular user agent around, and even if it were, the option wouldn't be on by default. Because of that, implementing this option would not affect mirror server loads. >> Do you mean that the first address in the list is malfunctioning? >> Shouldn't Wget then fall back to the next one? If one of the >> addresses is malfunctioning, even with --random you could still get >> that address, right? > > I don't see this behavior at all, if the first address returns > 404/403 I was talking about connection errors, not 404/403. Why would a mirror which is in DNS return 40x? That kind of error should be fixed on the server side, not by hacking Wget.
