Hi Nikhil,
Nikhil Marathe wrote:
Oops, I forgot to mention my connection details.
I'm NOT using a proxy, but I'm connected using Cyberoam client. In linux I'm running linc (linc.sf.net) and set up cron to force it to relogin every 3 minutes.
I am not sure about how running linc affects this, but if kget works so should any other client that support resume (ie: most of them).
You mentioned that ...
However wget, curl, axel, lftp when trying to resume, send the appropriate Range Header in HTTP/1.1 but fail to get a reply back. They wait for a long long time, still nothing.
I am assuming that by this you mean: a. You are downloading the files using http (if this is true, is there any specific reason why http instead of ftp ?) b. You used the -c (for wget) or -C (for curl) options (I don't know about the others). c. You are trying these clients for the same server that you use kget for. Since, the ability to resume downloads require server side capability to recognize and accept requests for files from a different offset that the start of the file.
If all of this is true, what is the response you get back from the server for your requests ?
regards, - steve