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

What protocol is being used in the right-clicked "save as"? Ftp managed by the browser? Http?

Whichever protocol is specified in the link. If the link says http://..., HTTP will be used. If the link says ftp://..., FTP will be used. The only difference is between clicking on the link normally and using save-as is what the browser does with the downloaded file. The former displays it, while the latter saves it to disk.

All major web browsers of the last eon should have both HTTP and FTP clients built in, so they can handle both HTTP and FTP links seemlessly.

Does this act appear in the web server log so that I can programmatically find and record the download data?

If HTTP is used, it'll appear in your web server logs.
If FTP is used, it'll appear in your FTP server logs.

Replies are listed 'Best First'.
Re^2: File download tool, file size issues, cgi-application
by cupojoe (Novice) on Mar 02, 2006 at 17:39 UTC

    Thanks for this. I think I was wondering if HTTP changed its behavior for larger files being downloaded and not displayed. If the browswer defaulted to ftp for the download, I wondered how that could affect me.

    Plus I'm looking to get some confidence that I'm approaching the application in a reasonable way. (link to the file rather than handling it directly via cgi.pm) It seems counterintuitive that the host will easily serve a huge download via http, but won't allow it via cgi (up or down - although I'm betting this is a security measure).