On Tuesday, January 31, 2017 11:24:33 AM CET Giuseppe Scrivano wrote: > Hi Tom, > > Tom Szilagyi <tomszila...@gmail.com> writes: > > Consider HTTP 503 (Service unavailable) as a non-fatal, transient > > error. Normally Wget gives up immediately on receiving this HTTP > > response. Certain special use cases might require Wget to retry even > > in the face of this error. With this option, such retries are > > performed subject to the normal retry timing and retry count > > limitations of Wget. Using this option is generally not recommended. > > thanks for working on it. If we are going to add something like this, I > think it should be made more generic. What about something like: > > --retry-on-http-error=503,504,505...
I think that this is a good idea. There are also 4xx and 9xx codes where retries could make sense (e.g. 429 - Too Many Requests) under certain conditions. The 503 response could contain 'Retry-After', a suggestion for the time of the next retry. Does it make sense to support it ? Tim
signature.asc
Description: This is a digitally signed message part.