Savut <we***@hotmail.com> wrote or quoted:
If someone can't use .htaccess because the hosting prohibit it, well I
suggest to change the hosting company because he miss a lot of features that
an .htaccess file can do. :D
Use of ".htaccess" is *often* turned off - on grounds of performance and
security [1].
I can't see why should I instruct people to change their site hosting so
they can run my software - when there's no need for me to force them to
do so.
Lastly, .htaccess is an apache-specific feature. Apache is not the
only PHP server in existence - and I would prefer my software to be
portable.
[1] ".htaccess files, Apache Tutorial"
``There are two main reasons to avoid the use of .htaccess
files.
The first of these is performance. When AllowOverride is set
to allow the use of .htaccess files, Apache will look in
every directory for .htaccess files. Thus, permitting
.htaccess files causes a performance hit, whether or not you
actually even use them! Also, the .htaccess file is loaded
every time a document is requested.
Further note that Apache must look for .htaccess files in
all higher-level directories, in order to have a full
complement of directives that it must apply. (See section on
how directives are applied.) Thus, if a file is requested
out of a directory /www/htdocs/example, Apache must look for
the following files:
/.htaccess
/www/.htaccess
/www/htdocs/.htaccess
/www/htdocs/example/.htaccess
And so, for each file access out of that directory, there
are 4 additional file-system accesses, even if none of those
files are present. (Note that this would only be the case if
.htaccess files were enabled for /, which is not usually the
case.)
The second consideration is one of security. You are
permitting users to modify server configuration, which may
result in changes over which you have no control. Carefully
consider whether you want to give your users this privilege.''
-
http://httpd.apache.org/docs/howto/htaccess.html
--
__________
|im |yler
http://timtyler.org/ ti*@tt1lock.org Remove lock to reply.