Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm currently using HTTP for pretty much all downloads. However the files on our UK based server is beings accessed by people all over the world often in 3rd world countries with dodgy internet connections (we give our software free to 3rd world countries).

The file is over 100MB in size and for a minority of people the HTTP download will think its complete after 0.5MB or some trivial amount. Repeated attempts to ask them to download again using HTTP after deleting their IE browser cache sometimes helps.

But what always works is to point them to the same file that they can download via FTP.

I'd always read that there was no advantage to using FTP over HTTP, but is there some kind of extra integrity checking that FTP uses? Is it worth just swapping completely over to FTP for our file downloads?

share|improve this question
up vote 3 down vote accepted

HTTP proxies can also limit object sizes or enforce timeouts.

share|improve this answer
Hmm, rather guiltily I think I've found my problem. I'd set the Timeout apache config to be 10 seconds (rather than the default of 300 seconds) so the http downloads have probably been timing out. Thus thank you for jolting my thoughts in the right direction. – icc97 Nov 21 '10 at 13:16

FTP can support download resume meaning if your client in South Africa downloads 99MB and gets cut off he can pick up where he left off. From the sounds of it you could benefit greatly from this.

However, it should be said that not all FTP clients support resume so you will most likely want to have some good documentation available for your clients.

share|improve this answer
HTTP provides for this too - though whether RANGE requests are implemented on the server is another question. – symcbean Nov 17 '10 at 12:49
Thanks for the comments. People are downloading using any browser they want (not FTP client) and the downloads don't stop half way through, the browser thinks the download is complete its just a tiny corrupted file – icc97 Nov 17 '10 at 14:24

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.