in reply to Re: File download tool, file size issues, cgi-application
in thread File download tool, file size issues, cgi-application

This looks good, but the OP stated that he can't serve files bigger than 2MB through any CGI script:
We can't count on them having ftp clients, and our web host (shared hosting) won't allow cgi driven downloads or uploads exceeding 2 megs. (I know, host sucks.)
  • Comment on Re^2: File download tool, file size issues, cgi-application

Replies are listed 'Best First'.
Re^3: File download tool, file size issues, cgi-application
by rhesa (Vicar) on Mar 02, 2006 at 20:55 UTC
    Right, I did gloss over that. in that case, there's no way to check that the download was successful at the time of download. The only option that remains is scanning the server logs, and checking if the downloaded size equals the file size. I'd probably give the download link a query param that makes it easy to pick it up from the logs.

      Yes, plus I'll know the unique filename. (assigned at upload)

      Is the server aware whether the client disconnects or whether there's any other physical interference, and therefore log something related to download failure?

        The only hint you'll likely be able to get is the reported download size. The log should say something like
        #ip address ... request status code size ... 10.10.10.10 ... "GET /your/file HTTP/1.0" 200 65536 ...
        The "size" field gives you the bytes sent. If the connection was broken mid-way, that value will be lower than your file size.

        See Apache access log for the full details.