I was thinking that a cookie could be set to allow the download and 
then if the file was asked to be download again it would see the 
cookie and deny the download. This method is not perfect, as one  
could simply move to a laptop or another computer and request the 
download again, thus getting the file twice with an access code if 
.htaccess was used.

What I need to do, and I neglected to mention in my first post, is 
protect a software product download that a client is selling on the 
net. I suggested a shopping cart that allowed downloads, but the 
client doesn't want to spend the money for a shopping cart that can 
do this. 

They are hoping that there is another method for them to encrypt 
the credit card on an ssl layer using a form, then perhaps return a 
code via email that would unlock the file for download or have a 
script that would limit the number of downloads. (Hum, sounds like 
they want a poor-man's shopping cart!)

Thanks for your suggestions!

Jim H


> I don't see how this would work unless the used password info is
> stored on the server somewhere, which would necessitate the need for
> cgi, php, or something similar.  Simple javascript without writing to
> a file somewhere to compare the used passwords against is not going to
> be possible as far as I know.

HTML: hwg-basics mailing list archives, maintained by Webmasters @ IWA