does using passowrds carry a performance hit with Apache?

does using passowrds carry a performance hit with Apache?

Post by Cryptoniu » Wed, 08 Mar 2000 04:00:00



I have a web site running on Apache 1.3.x and to try and protect my
files from being linked to I protected the dirs they're in and added
the login+password in the link. The idea being that constantly
changing the login+password in the files and server is a small
deterrent against linking.

But now I have a feeling that the server is getting slower with all
this authentication but I have no data on this issue. Does anyone have
info on this? I'm using only one user/password but will I get a
performance increase by discarding this whole scheme?

I can live with a small performance hit but with tens of thousands of
files being requested every day I want to know how much of a hit I'm
suffering.

Thanks for any info on the matter.

Cryptonium

 
 
 

does using passowrds carry a performance hit with Apache?

Post by Joshua Sliv » Wed, 08 Mar 2000 04:00:00



> I have a web site running on Apache 1.3.x and to try and protect my
> files from being linked to I protected the dirs they're in and added
> the login+password in the link. The idea being that constantly
> changing the login+password in the files and server is a small
> deterrent against linking.
> But now I have a feeling that the server is getting slower with all
> this authentication but I have no data on this issue. Does anyone have
> info on this? I'm using only one user/password but will I get a
> performance increase by discarding this whole scheme?
> I can live with a small performance hit but with tens of thousands of
> files being requested every day I want to know how much of a hit I'm
> suffering.

To the best of my knowledge, your main problem is going to be that the
login+password "in the link" (I assume you mean

You may very well be excluding people from your site using this.

Why not just change the directory or file names, instead of messing
with authentication.

The actual performance hit to the apache server is probably minimal,
but you are also preventing caching by using authentication, which
could result in a substantial perceived performance hit versus just
changing the directory name every few days.

--
Joshua Slive

http://finance.commerce.ubc.ca/~slive/

 
 
 

does using passowrds carry a performance hit with Apache?

Post by Nick K » Wed, 08 Mar 2000 04:00:00




Quote:

> But now I have a feeling that the server is getting slower with all
> this authentication but I have no data on this issue.

The effect on the server itself is negligible.

However, from (some) users point of view, it's going to be much slower,
because password-protecting a page will inhibit (public) cacheing.

--
Nick Kew

We're so advanced here ... our nearest main road is called the A 386