Description of Problem: I tried to download a file and had to stop it. Next time I had network I used wget, this time with -c option to continue (otherwise it gets from zero to a new file). The network became unstable, and there was a timeout, so wget tried again, but complained that there was a problem with "-c". So I wonder why the first try always work, but try 2 fails. It seems related to "reusing connection", cos it does not happen when "connecting" is printed (IOW, if for whatever reason it must reconnect, wget can download partially downloaded files and do so with multiple tries if needed). Version-Release number of selected component (if applicable): How Reproducible: Always that -c is used with a partially downloaded file and there is a time out, and the server is capable of keeping connections open. Steps to Reproduce: 1. get part of a file from an Apache server, for example 2. continue the download with -c option 3. make the transfer stall so wget tries again, reusing the connection Actual Results: [error downloading an already partially downloaded file] xx:xx:xx (x KB/s) - Read error at byte x/x (Connection timed out). Retrying. --13:17:44-- http://x.x.x/x.x (try: 2) => `x.x' Reusing connection to x.x.x.x:x. HTTP request sent, awaiting response... Continued download failed on this file, which conflicts with `-c'. Refusing to truncate existing file `xxx.x'. And now the user has to launch wget again and pray that it can download without more problems, or he will have to relaunch and relauch, instead of using the max tries option. Expected Results: -c should work if the file was cut and the user wants to keep on downloading. As is, -c is a pain with faulty servers or nets, cos everytime there is a problem the user must relauch. Additional Information: In older versions the -c worked, probably cos there was no connection reusing, or the interaction of reuse and partial was coded right. You set a number of retries and it worked, not failed in the 2nd try, be the file new or restarted from a partial download.
Is this still a problem with the version in RHL 7.3?
Yes, seems so now, I have not saw it since I updated a couple weeks or so ago. 1.8.1 seems fine, closing, if it reappears, I will open it again.