Our philosophy is "if it ain't broke, don’t fix it" - hence 8 years with v7.15.
However, I ran a couple of interrupted FTP downloads with Verbose logs. The REST command seems the source of the problem. With v7.15.5, which works fine, we see > REST 47152[CR] but with v7.37.1, which don’t > REST 40544 [CR] i.e. there's an extra space character after the offset, which the server (MS IIS) rejects, returning 501 & showing in its log REST 40544+ Dave -----Original Message----- From: curl-library [mailto:[email protected]] On Behalf Of Daniel Stenberg Sent: 03 October 2014 12:47 To: libcurl development Subject: Re: FTP resume libcurl 7.15 to 7.37 On Thu, 2 Oct 2014, Bentham, Dave wrote: > A recent modification to our system is to allow similar downloads over GSM > which is a bit more flaky. One of the enhancements was to upgrade libcurl to > the latest, v7.37.1, and whilst early indications suggest the FTP as a whole > is slightly faster and more reliable, resuming interrupted downloads always > fails straight off with an error code 31, REST command failure. I can't find > anything obviously different in programming libcurl between 7.15 & 7.37. > > curl_easy_setopt(curl, CURLOPT_RESUME_FROM, > (long)#(ftpResumeFrom)); Wow, that's a 8+ years bump! It'll help us if you tell us exactly what happens, protocol wise, when it fails. Perhaps a CURLOPT_VERBOSE output log. I would guess that if you'd do a similar dump using your old lib version and compared the two that might offer some clues. -- / daniel.haxx.se ------------------------------------------------------------------- List admin: http://cool.haxx.se/list/listinfo/curl-library Etiquette: http://curl.haxx.se/mail/etiquette.html ------------------------------------------------------------------- List admin: http://cool.haxx.se/list/listinfo/curl-library Etiquette: http://curl.haxx.se/mail/etiquette.html
