Bugs item #3593336, was opened at 2012-12-06 13:26
Message generated for change (Comment added) made by bagder
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100976&aid=3593336&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: client module
>Group: wrong behaviour
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: john (jrem)
>Assigned to: Daniel Stenberg (bagder)
Summary: curl -LOJC- http://url doesn't resume as expected

Initial Comment:
curl version:
curl 7.28.1 (x86_64-pc-win32) libcurl/7.28.1 OpenSSL/1.0.0j zlib/1.2.7 WinIDN libssh2/1.4.2 librtmp/2.3
Protocols: dict file ftp ftps gopher http https imap imaps ldap pop3 pop3s rtmp rtsp scp sftp smtp smtps telnet tftp
Features: AsynchDNS GSS-Negotiate IDN Largefile NTLM SSL SSPI libz

windows 7 x64 home premium

I like to use curl to download large files, and rely on the resume to restart download if it breaks. Nowadays many of the urls dont include the actual filename anymore, eg downloading from ubuntuone the url looks like http://ubuntuone.com0pYiteewbQWcKU70E

previously I used curl -LOC- http://url and it worked fine, except the resulting filename not always correct. trying to use curl -LOJC- http://url almost works except you lose resume capability as shown below.

I would like to use the J option to get correct filename written but without losing resume support.

I note that varying order of options leads to varying results, but experimentation gives this as best so far unless I've missed something.

C:\Users\john\Downloads\d>curl -LOJC- http://ubuntuone.com/0pYiteewbQWcKU70E
  % Total % Received % Xferd Average Speed Time Time Time Current
                                 Dload Upload Total Spent Left Speed
  0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0Warning: Refusing to overwrite 3DKDirect-Burn.exe: Fil
e exists
  0 1175M 0 890 0 0 750 0 19d 00h 0:00:01 19d 00h 1037
curl: (23) Failed writing body (0 != 890)

John

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

>Comment By: Daniel Stenberg (bagder)
Date: 2012-12-10 01:19

Message:
Right, since it doesn't know the actual target file name until way down the
line it is a problem indeed...

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

You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100976&aid=3593336&group_id=976
Received on 2012-12-10