Complete Guide to Enabling mod_rewrite in Apache 2.2

Overview of Apache mod_rewrite Module

mod_rewrite is a powerful Apache HTTP Server module designed to dynamically modify incoming URL requests based on regular expression rules. The module supports unlimited rules and conditions, enabling highly flexible URL mapping and rewriting capabilities. Through mod_rewrite, developers can map arbitrary URLs to internal URL structures, operate on full URLs (including path information and query strings), and apply configurations at server, virtual host, or directory levels.

Core Steps to Enable mod_rewrite

Enabling mod_rewrite in Apache 2.2 requires three key steps: module loading, service restart, and permission configuration. First, ensure the module is properly loaded. On Debian/Ubuntu-based systems, use the sudo a2enmod rewrite command; on other systems, manually edit the httpd.conf file and uncomment the LoadModule rewrite_module modules/mod_rewrite.so line.

Apache Service Restart Methods

After enabling the module, Apache service must be restarted for changes to take effect. Depending on the system environment, choose from these restart commands: sudo /etc/init.d/apache2 restart for traditional init systems; sudo service apache2 restart for newer service management; sudo systemctl restart apache2 for modern Linux distributions using systemd. After restarting, verify rewrite_module loading with apache2ctl -M or httpd -M commands.

Detailed .htaccess File Configuration

Creating a .htaccess file in the DocumentRoot directory is a common approach for URL rewriting. A complete configuration example follows:

<IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php [L]
</IfModule>

This configuration starts with RewriteEngine On to enable the rewrite engine, and RewriteBase / sets the base path. The two RewriteCond conditions check if the requested file and directory exist; if neither exists, RewriteRule redirects all requests to index.php, with the [L] flag indicating this is the last rule.

Critical Virtual Host Configuration Settings

If rewrite rules in .htaccess don't work, directory permission configuration is likely the issue. Add AllowOverride All in the <Directory> section of virtual host configuration to allow .htaccess to override server settings. A complete configuration example:

<VirtualHost *:80>
    DocumentRoot /var/www/html
    <Directory /var/www/html>
        AllowOverride All
        Require all granted
    </Directory>
</VirtualHost>

Troubleshooting Common Issues

When mod_rewrite rules fail, systematically check multiple aspects. First, confirm module loading via Apache's module list command. Second, ensure .htaccess is in the correct DocumentRoot directory with proper read permissions. Then verify AllowOverride All is set in virtual host configuration. Finally, check rewrite rule syntax correctness and consult Apache error logs for detailed debugging information.

Practical Application Scenarios

Consider a typical web application directory structure: httpdocs as DocumentRoot containing .htaccess, index.php, and static resource directories like images, js, and css. Application logic files reside in includes/app. With the above configuration, all non-existent file requests redirect to index.php while static resources serve normally, implementing a front controller pattern.

Performance Optimization and Best Practices

While .htaccess files offer convenient configuration, production environments benefit from placing rewrite rules directly in virtual host configuration to avoid performance overhead from reading .htaccess on each request. Additionally, complex rewrite rules should be broken into simpler ones, using flags like [NC] (case-insensitive) and [R=301] (permanent redirect) to optimize matching efficiency.