|The stupid question is the question not asked|
File download tool, file size issues, cgi-applicationby cupojoe (Novice)
|on Mar 02, 2006 at 16:53 UTC||Need Help??|
cupojoe has asked for the
wisdom of the Perl Monks concerning the following question:
It's a small project, and I'm pretty green to Perl.
It's an architecture and reality check question. Hope you don't mind.
Building a section of a web site so logged in users can download files we've uploaded for them to get. The files are 10 - 20 megabytes (pdf'd engineering reports).
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.)
The current plan is, we'll ftp the file up, and my tool will provide a link so they can right-click and "save as".
(linux, apache, mod_perl, cgi-application and session plugin, HTML-Template, dbi, mysql.)
Originally, I wanted to control the download so we had as much positive info as possible that it was downloaded, date/time, IP address, login id etc. Since it doesn't look like I can use cgi.pm to drive the download, or the upload, and they're likely to not have an ftp client or know how to use it - the right clicked link appears reasonable.
Unless I'm missing something.
What protocol is being used in the right-clicked "save as"? Ftp managed by the browser? Http?
Does this act appear in the web server log so that I can programmatically find and record the download data?
I've spent a good deal of time in various searches here at Perlmonks, MS knowledge base, and others, and feel I've run out of even knowing where else to look.
Thanks in advance!