Bugs item #3037362, was opened at 2010-07-30 23:27
Message generated for change (Tracker Item Submitted) made by dodtsair
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100976&aid=3037362&group_id=976

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Mike Power (dodtsair)
Assigned to: Nobody/Anonymous (nobody)
Summary: Using -f ignores --retry

Initial Comment:
curl -V
curl 7.19.7 (i386-redhat-linux-gnu) libcurl/7.19.7 NSS/3.12.6.2 zlib/1.2.3 libidn/1.9 libssh2/1.2.2
Protocols: tftp ftp telnet dict ldap ldaps http file https ftps scp sftp
Features: GSS-Negotiate IDN IPv6 Largefile SSL libz

This may have already been reported but searching for "curl f retry" does not go very far.

When using the -f option curl does not attempt to retry the URL on a 503 instead it immediately returns the first failure.

I would be great if curl could rety the url then when it finally fails return the error for it. I can write a retry loop myself and will but it would have been nice since curl can already retry to have it do the work for me

To reproduce
curl --retry-delay 2 --retry 3 -m 10 'someURLthat503s' -o /tmp/tmp.LYMrNZqaVY;

#this tries 4 times and then returns 0

curl -f --retry-delay 2 --retry 3 -m 10 'someURLthat503s' -o /tmp/tmp.LYMrNZqaVY;
#this tries 1 time and then returns 22

Desired behavior
curl -f --retry-delay 2 --retry 3 -m 10 'someURLthat503s' -o /tmp/tmp.LYMrNZqaVY;
#this tries 4 times and then returns 22

Implications forces retry coding onto scripts

----------------------------------------------------------------------

You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100976&aid=3037362&group_id=976
Received on 2010-07-31