I am wondering about the impact of protection by htaccess for a "given" perl file.

Assume Apache as the web server, Linux or Windows as the OS.

I want to protect 1 perl file only with htaccess in a given directory.

Example :

Case 1 : /cgi-bin dir with 4 perl files and 1 protected by htaccess.

Case 2: /cgi-bin dir with 3 perl files and /cgi-bin/secure/ 1 perl file and 1 protected file.



The protected file will be used occasionally by Admin people only to change setting's.

The rest of the perl files are used regularly by the "web people" doing normal business.

I have read the documentation on how htaccess works but I do not see a way to log this, or

view a log of this activity.

Am I better off with Case 1 or Case 2 ? with respect to the lowest impact on the regular web people.

Or is there a better way to do this ?

Thanks

Kode

You're better off with method 2 and then you will have to analyze your log files yourself. But using a sepeare directory makes this a lot easier on the eye.

- wil

Thanks Wil

I am trying to use the lowest impact for the web people in general.

The documentation seems to imply that it searches from the root onwards.

What I am trying to realise is if the htaccess file is in a directory in front of usual business

does it make an impact if not needed ?

Example:

Say a call comes in to http//mysite/cgi-bin/counter.pl?add=1... [generic (-: ]

1. Having an htaccess for Admin.pl in the /cgi-bin/secure/ does this have

an affect on the file counter.pl in the cgi-bin dir by the process of the web server

looking for other htaccess files along the route to this or any file on the route ?

Or Should I just add more RAM [ microsoft technique ].

Thanks

Kode

Add more RAM? Whoever suggested that?

.htaccess control files in the directory where the .htaccess file is in and all directories beneath that.

For example, if I have a .htaccess file in:

/html/protected/

It will imply it's powers to all the following:

/html/protected/
/html/protected/foo/
/html/protected/foo/bar/

And so forth. But it will not have an impact on anything beneath this. So the following directories will be not be controlled by the .htaccess file above:

/html/
/html/public/
/html/public/foo/

Hope this helps.

- wil

How about adding a meta-refresh (or .htaccess if supported) in place of the file that needs to be put into a seperate folder for protection? Just an idea

Andy (mod)
andy@ultranerds.co.uk

---

Want to give me something back for my help? Please see my Amazon Wish List
GLinks ULTRA Package | GLinks ULTRA Package PRO
Links SQL Plugins | Website Design and SEO | UltraNerds | ULTRAGLobals Plugin | Pre-Made Template Sets | FREE GLinks Plugins!