View Single Post
Old 30th November 2005, 05:15
crudolphy crudolphy is offline
Join Date: Nov 2005
Location: The Woodlands (Near Houston) Texas USA
Posts: 40
Thanks: 1
Thanked 0 Times in 0 Posts
Question .htaccess

It seems that this has become two issues so I will keep this thread going on the .htaccess issue which could conclude quickly and start a new thread for the error messages above.

Regarding .htaccess. I read this afternoon a short tutorial from the Apache Web Site. It states,

"In general, you should never use .htaccess files unless you don't have access to the main server configuration file."

Later on they say,

"However, in general, use of .htaccess files should be avoided when possible. Any configuration that you would consider putting in a .htaccess file, can just as effectively be made in a <Directory> section in your main server configuration file."

Because this is my machine I have access to the main configuration, so I could do away with the .htaccess file completely by making those changes directly. This would be method #1 of solving this.

In the /etc/apache2/apache2.conf there are several places where .htaccess files are discussed. Once in a <files></files> section and also in all of the <directory></directory> sections. In every case the directives contained are:

Order allow,deny
Deny from all

Now I understand why I got the http 500 internal server error.

One way to correct this would be to change the <Directory></Directory> section relating to for all virtual hosts, i.e. /var/www/*/web/ and change the statement to:

Allow from all

Due to the statements in the .htaccess file I would also have to make sure this section included a

AllowOverride FileInfo

statement, which I believe it does.

This would be method #2 of solving this.

My questions are:

Are my statements regarding method #1 and method #2 above correct?

In ISPConfig there is a section ("Apache Directives") for the ISPConfig adminstrator to enter in specfic directives for each virtual host. These directives I believe are stored in the /etc/apache2/vhosts/Vhosts_ispconfig.conf file, is this correct?

Could a custom <directory></directory> section be entered in this section that pertained to the /var/www/web1/web/egroupware directory, listing the specific directives for just that directory, thus eliminating the need for the .htaccess file?

Looking at the /etc/apache2/vhosts/Vhosts_ispconfig.conf file I see several statements that are similiar in nature to the directives contained in this .htaccess file. Would it be possible to place the directives contained in the .htaccess file directly in "Vhosts" file by hand or via the ISPConfig "Apache Directives" configuration page?

Lastly which of the methods that you identify as correct would in your opinion be the best way to address this?

Your help is very much appreciated.

Chuck Rudolphy
Reply With Quote