[bug #20417] 503 respose is not retryable but should be

2020-03-11 Thread Tim Ruehsen
Follow-up Comment #8, bug #20417 (project wget): Please open a new issue with a detailed description - and if possible with a log file (options: --debug -olog.txt) and/or reproducer. ___ Reply to this item at:

[bug #20417] 503 respose is not retryable but should be

2020-03-11 Thread anonymous
Follow-up Comment #7, bug #20417 (project wget): Also, this bug is decidedly NOT fixed, as Retry-After is simply ignored and wget immediately retries, hammering the server. ___ Reply to this item at:

[bug #20417] 503 respose is not retryable but should be

2020-03-11 Thread anonymous
Follow-up Comment #6, bug #20417 (project wget): While wget now supports --retry-on-http-error, using it breaks both the HTTP spec and the intent, as wget still ignores Retry-After completely and pretty much retries instantly in a loop, which is very bad behaviour and not approrpiate for an

[Bug-wget] [bug #20417] 503 respose is not retryable but should be

2017-02-12 Thread Tim Ruehsen
Update of bug #20417 (project wget): Status: Invalid => Fixed Fixed Release:None => 1.19.1 ___ Reply to this item at:

[Bug-wget] [bug #20417] 503 respose is not retryable but should be

2017-02-12 Thread anonymous
Follow-up Comment #5, bug #20417 (project wget): Starting with version 1.19.1, Wget supports the option --retry-on-http-error which you can use to specify a list of HTTP error codes that should be retried. So, provided that you are running a current version of wget, just add this to the