Forum Moderators: phranque

Message Too Old, No Replies

Pros & Cons of working above DocumentRoot

documentroot

         

zeuf

5:46 pm on Nov 24, 2008 (gmt 0)

10+ Year Member


Hi everybody from Paris !

This is my first post here. I discovered WW thanks to Google. I think that you guys are pretty cool and clever, always helping. Congratulations, truely. First, I want to tell that I did my search on the forum first (and on the web also !).

As I am french I will try to do my best to be clear. Here I am : I'm working on a new project and I want to use folders above DocumentRoot to work with (/pictures/www for example) because I do not want to work with .htaccess anymore (in /www/pictures for example). Neither I want to use uniqid-md5-reuniqid-remd5 to code names of pictures and folders under /www. So I decided to work above the DocumentRoot.

Here are my questions :

1. Who already worked like that with approx. access to a library of 10.000 to 100.000 pictures (of course not a the same time. Around 3000 to 4000 users).
2. As PHP must use readfile to get the picture, does it take a lot of CPU Process ?
3. Is it as secure as a .htaccess file (for a normal user of course) ?
4. Is it a normal way (or another good way) to protect Gigas of datas ? Or is it a bad way (and why, of course) ?

I find it easy enough to work like that, that is why I am asking you (as my clients are fed up with .htaccess login to secure their pictures).

Thank you very much all of you for your patience and for your experiences and help.

Zeuf

henry0

11:30 pm on Nov 25, 2008 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Zeuf welcome to WebmasterWorld!
FR:
Je n'ai pas utilise cette methode pour une large quantite de files.
Mais l'utilise pour isoler de root ma DB connection file.
c'est une methode tres sure!

EN:
I never fetched a large amount of files from www/html/
However I use this method to call my DB conn script and keep it away from root

Have a drink on me "a la Coupole" :)