Re: [WebDNA] directory protection questions
This WebDNA talk-list message is from 2008
It keeps the original formatting.
numero = 100241
interpreted = N
texte = 1) This is how I have been doing it for the past several years. First I name everything normally cindy01.jpg, cindy02.jpg, etc.; then I append 4 random numbers after every file so they are now cindy018471.jpg, cindy029450.jpg. It works fine, and I don't mind mind leaving it as is if I have to. 2) Not an option in my case; everyone is accessing the same files*. I do this when they sign up, however, and create a file named after their cart. When it's been hit once (i.e., they activated their account), then the file is deleted. Actually, the file is renamed, then deleted automatically after a few days (longer if I don't hit the page daily that has the delete file thingie on it) *The site is a foot fetish website, and I upload 75-100 pictures every week or so. I have a directory that contains all the libraries, which contain all the images. There are around 40,000 images by now. It would be nice to just be able to turn people away with authentication when they come cruising for free images. Terry >Terry Wilson wrote: >> Can someone point me in the right direction for managing directory >>protection with WebDNA? Not page protection... directory >>protection. I have libraries full of images on a pay-site, and >>would like to get this matter resolved once and for all. It needs >>to happen in real-time so people can gain access instantly. > >I can think of two ways of doing something similar: > >1) Random file names >Just choose file names that aren't easy to guess. >This is a simple low security solution and works well if the >customer is supposed to have permanent access to the file once >he/she has paid for it. > >2) [COPYFILE] >Keep the original files hidden at all times and create temporary >copies for each customer. >It's not exactly real-time but provided the files are reasonably >small, we're talking only a few seconds delay. >You better make sure the server can handle it though. If you have a >lot of customers, you'll end up with some serious disc and processor >load. >Oh, and remember to add a script for deleting the temporary files >after a set amount of time too! > > > >Frank Nordberg >http://www.musicaviva.com >http://stores.ebay.com/Nordbergs-Music-Store?refid=store -- Terry Wilson | terry@terryfic.com | http://terryfic.com http://WhosComing.com - a simplified, affordable online reservation system http://TightJacket.com -- stylish protection for your laptop -------------------------------------------------------------------------- Attitude is the only difference between ordeal and adventure.
Associated Messages, from the most recent to the oldest:
1) This is how I have been doing it for the past several years. First I name everything normally cindy01.jpg, cindy02.jpg, etc.; then I append 4 random numbers after every file so they are now cindy018471.jpg, cindy029450.jpg. It works fine, and I don't mind mind leaving it as is if I have to. 2) Not an option in my case; everyone is accessing the same files*. I do this when they sign up, however, and create a file named after their cart. When it's been hit once (i.e., they activated their account), then the file is deleted. Actually, the file is renamed, then deleted automatically after a few days (longer if I don't hit the page daily that has the delete file thingie on it) *The site is a foot fetish website, and I upload 75-100 pictures every week or so. I have a directory that contains all the libraries, which contain all the images. There are around 40,000 images by now. It would be nice to just be able to turn people away with authentication when they come cruising for free images. Terry >Terry Wilson wrote: >> Can someone point me in the right direction for managing directory >>protection with WebDNA? Not page protection... directory >>protection. I have libraries full of images on a pay-site, and >>would like to get this matter resolved once and for all. It needs >>to happen in real-time so people can gain access instantly. > >I can think of two ways of doing something similar: > >1) Random file names >Just choose file names that aren't easy to guess. >This is a simple low security solution and works well if the >customer is supposed to have permanent access to the file once >he/she has paid for it. > >2)
[copyfile] >Keep the original files hidden at all times and create temporary >copies for each customer. >It's not exactly real-time but provided the files are reasonably >small, we're talking only a few seconds delay. >You better make sure the server can handle it though. If you have a >lot of customers, you'll end up with some serious disc and processor >load. >Oh, and remember to add a script for deleting the temporary files >after a set amount of time too! > > > >Frank Nordberg >http://www.musicaviva.com >http://stores.ebay.com/Nordbergs-Music-Store?refid=store -- Terry Wilson | terry@terryfic.com | http://terryfic.com http://WhosComing.com - a simplified, affordable online reservation system http://TightJacket.com -- stylish protection for your laptop -------------------------------------------------------------------------- Attitude is the only difference between ordeal and adventure.
Terry Wilson
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
[WebDNA] PayPal Integration (2017)
netstat -a on downed server (2004)
RE: [input] questions (1997)
Using Cookie for client specific info? (1997)
A Global Variable (1997)
Incorrect Value Display (2000)
Multiple prices (1997)
Attn: Bug in GeneralStore example b15 (1997)
Duplicate Items in the Cart (1998)
Multiple fields on 1 input (1997)
Webcatalog error, Plug-in for Webstar (1996)
StoreBuilder Shopping Cart (2000)
WC2b15 - [HTMLx]...[/HTMLx] problems (1997)
How true is this? (1999)
Emailer (1997)
RE: Clearing orders and database help! (1997)
PCS Frames (1997)
Add a field to the error log? (1997)
b12 cannot limit records returned and more. (1997)
Rubbish in form fields (2004)