Linux – I have no “AllowOverride” directive in the apache2.conf

.htaccessapache-2.2linuxmod-rewritePHP

I have viewed my httpd.conf and apache2.conf and I have no AllowOverride directive in either of the files.

The .htaccess works fine. I have a bunch of rewrites in it, so I know it works.

Is apache2 by default set to "AllowOverride All"?

Anybody know if I should add this? Or if it would hurt to add it?

The reason for all this is that I get a bunch of errors in my apache2 error log.

Thanks

Best Answer

It is not an issue of AllowOverride(yes, Apache's default is All)
It's simply a logging of the fact, that a file was'nt found, an 404-error. You should find the same entry inside the access_log.

If you don't have further problems with this logging(maybe your space is rare, so you have to avoid it), you could leave it as it is. If you don't want errors of the level "error" to be logged, you can modify the log-level inside httpd.conf. Find the line starting with LogLevel . Change the following word(maybe: warn, error, notice, info, debug) to crit ->then restart the server.

But do this only if you have good reasons, because if you do this you don't get any error-level-errors logged in the future, and there are more errors than missing files.

Regarding to the question how to add AllowOverride: you can put these directives onto httpd.conf inside every <directory/>-Section. For example:

<directory "path/to/htdocs">
#some stuff
AllowOverride None
#more stuff
</directory>

Related Solutions

Linux – .htaccess not working (mod_rewrite)

Try putting the rewrite rules directly into the VirtualHost config section (not under a "Directory" rule)

This way you can bypass any problems that may be cause by .htaccess and path identification mechanisms.

Check if rewrite_module is loaded into apache:

apache2ctl -t -D DUMP_MODULES

If not enabled, enable the mod_rewrite with

a2enmod rewrite

This will set up necessary links under mods-enabled (not mods-available)

.htaccess is ignored even though VirtualHost has “AllowOverride All”

Unbelievable. Remember how I said this is a development server? Yeah.. well here's what my virtual host entry REALLY looks like:

<VirtualHost *>
    ServerName              dev.ourwebsite.com
    DocumentRoot            /var/www/html/dev.ourwebsite.com/docroot
    <Directory "/var/www/html/ourwebsite.com/docroot">
        Options FollowSymLinks
        AllowOverride All

        Order allow,deny
        Allow from all
    </Directory>
</VirtualHost>

Do you see it? Well I didn't. I FORGOT To change my "Directory" entry to dev.ourwebsite.com instead of ourwebsite.com -- and that made all the difference. I just assumed that Apache would have thrown an error if the directory didn't exist; but that only applies to the DocumentRoot directive. is match-based -- meaning it applies the rules if it matches the incoming request, but otherwise, it doesn't care if you tell it to AllowOverride on magic unicorns.

Let this be a lesson to any others who come looking -- when all else fails, consider the almighty Typo.

Best Answer

Related Solutions

Linux – .htaccess not working (mod_rewrite)

.htaccess is ignored even though VirtualHost has “AllowOverride All”

Related Topic