Not sure what's the question or the answer below... but anyway. To protect your files, store them outside of the webroot or in the database and use a PHP file to serve them up. The PHP file will check the authentication or whatever of the user and if it's valid, serve up the file to them with a proper header() call and sending the data of the file. ---John W. Holmes... PHP Architect - A monthly magazine for PHP Professionals. Get your copy today. http://www.phparch.com/ > -----Original Message----- > From: Gary.Every@ingramentertainment.com > [mailto:Gary.Every@ingramentertainment.com] > Sent: Thursday, January 09, 2003 9:56 AM > To: darren@bcgroup.net; isp-webhosting@isp-webhosting.com > Cc: isp-linux@isp-linux.com; php-db@lists.php.net > Subject: RE: denying access to folders/files > > > > Gary Every > Sr. UNIX Administrator > Ingram Entertainment > (615) 287-4876 > "Pay It Forward" > mailto:gary.every@ingramentertainment.com > http://accessingram.com > > > This is fine and dandy, but how do I prevent that person from taking the > direct link to the file and giving it to someone else? > > I'm sure there is a much better and simpler way. Idea's? > > Answer: Use auto_prepend.php to authenticate the user. > > > Thanks in advance. > > -- > Darren Bentley <darren@bcgroup.net> > > > -- > PHP Database Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php -- PHP Database Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
