[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Wget-dev] wget2 | WIP: Implement a --retry-on-http-status switch (!

From: Tim Rühsen
Subject: Re: [Wget-dev] wget2 | WIP: Implement a --retry-on-http-status switch (!381)
Date: Tue, 03 Jul 2018 10:02:02 +0000

> Then, if the user gives something like: $ wget2
> --retry-on-http-status=200 google.es
> Should wget2 fall into a endless loop?

200 is a special case. The idea behind --retry-on-http-status was to be more 
flexible with 'final errors'. E.g. some proxies send them wrong - but the user 
knows better and would like to retry.

So we can
- disallow 200 with --retry-on-http-status
- treat 200 as an error (--tries would prevent an endless loop, we don't save a 
- treat 200 as OK (=save file), increase the retry counter like in the error 
case and do the request again until the retry counter expires. This leads to 
`file`, `file.1`, ...

IMO, for now we can disallow 200 to keep the code simple. If people *really* 
want/need it we can change the behavior.

Reply to this email directly or view it on GitLab: 
You're receiving this email because of your account on gitlab.com.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]