[Bug-wget] [bug #56992] Support --retry-on-http-error ranges

Follow-up Comment #4, bug #56992 (project wget): [comment #0 original submission:] > It would be practical if wget supported ranges for “--retry-on-http-error” natively, in combination with individual numbers. > > Example: > > wget example.org --retry-on-http-error=400-600 > wget example.org

[Bug-wget] [bug #56992] Support --retry-on-http-error ranges

Follow-up Comment #3, bug #56992 (project wget): [comment #1 comment #1:] > Wget2 has something like --retry-on-http-status (we likely rename that to --retry-on-http-error before the next beta release) > > Specify a comma-separated list of HTTP codes in which Wget2 will retry the download. The

[Bug-wget] [bug #56992] Support --retry-on-http-error ranges

Follow-up Comment #2, bug #56992 (project wget): [comment #1 comment #1:] > Wget2 has something like --retry-on-http-status (we likely rename that to --retry-on-http-error before the next beta release) > > Specify a comma-separated list of HTTP codes in which Wget2 will retry the download. The

[Bug-wget] [bug #56909] wget Authorization header leak via 3xx redirects

Update of bug #56909 (project wget): Privacy: Private => Public ___ Follow-up Comment #4: I agree with Tim here that this is not a security issue. Wget provides an option to correctly use

[Bug-wget] [bug #56992] Support --retry-on-http-error ranges

Follow-up Comment #1, bug #56992 (project wget): Wget2 has something like --retry-on-http-status (we likely rename that to --retry-on-http-error before the next beta release) Specify a comma-separated list of HTTP codes in which Wget2 will retry the download. The elements of the list may

[Bug-wget] [bug #56992] Support --retry-on-http-error ranges

URL: Summary: Support --retry-on-http-error ranges Project: GNU Wget Submitted by: None Submitted on: Fri 04 Oct 2019 01:11:10 PM UTC Category: None Severity: 3 -

[bug #56987] Please add the highly demanded “--retry-on-http-error” feature.

Update of bug #56987 (project wget): Status:None => Invalid Open/Closed:Open => Closed ___ Reply to this item at: