Re^3: File download tool, file size issues, cgi-application

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.

Comment on Re^3: File download tool, file size issues, cgi-application

Replies are listed 'Best First'.
Re^4: File download tool, file size issues, cgi-application by cupojoe (Novice) on Mar 02, 2006 at 23:54 UTC
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?	[reply]
Re^5: File download tool, file size issues, cgi-application by rhesa (Vicar) on Mar 03, 2006 at 00:10 UTC
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 ...` [download] 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.	[reply] [d/l]
Re^6: File download tool, file size issues, cgi-application by salvix (Pilgrim) on Mar 03, 2006 at 15:52 UTC
Also watch out for status code 206, it is the "Partial Content" status code. In other words, it means the browser asked for a byte-range of data because it already had some data (e.g.: if the connection was interrupted during the download). So your log may also have a status code 206 and the size won't match the total file size... Oh, wouldn't it be easier if your ISP allowed "full" CGIs?? :-P	[reply]
Re^6: File download tool, file size issues, cgi-application by cupojoe (Novice) on Mar 03, 2006 at 00:20 UTC
Very good. Thanks for your help!	[reply]