I then wanted to restrict downloads through this script, so that people cannot know the real location of the file and download it directly.
It seems to me that web users will only be able to download your files directly if you place them in a virtual directory or if you have ftp turned on. I know from experience that is the case with the Oracle Application Server webserver—it will reject as invalid any path that you have not previously specified as a valid one.
Pulling out my copy of Apache Server for dummies, I see that such is the case for Apache Server as well. The book says that:
The resource configuration file, srm.conf: This file usually contains things that define where documents are found, how to translate Web addresses to file names, and so onYour Perl script will know the locations of your files and can open and read them server side. Your web users will not be able to download the files because there will not be any valid URL pointing to them.
In reply to Re: Specifying filename for download
by sierrathedog04
in thread Specifying filename for download
by Chady
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |