Resolving the Issue of index.php Not Loading by Default in Apache Server

Problem Description and Background

After deploying Apache and PHP on a CentOS system, accessing the website directory at http://example.com/myapp/ results in a "forbidden" error, while directly accessing http://example.com/myapp/index.php displays the page correctly. This indicates that the Apache server is not properly recognizing index.php as a default index file.

Core Configuration Principles

The Apache server uses the DirectoryIndex directive to define which files should be loaded by default when a request points to a directory. The default configuration typically includes only index.html, so it is necessary to explicitly add index.php to ensure PHP files are automatically loaded.

Solution Comparison

Configuration Using .htaccess File

Create a .htaccess file in the web root directory and add the following content:

DirectoryIndex index.php

This method is simple and quick, especially suitable for shared hosting environments. However, it is important to ensure that Apache has the AllowOverride directive enabled to read .htaccess files.

Modifying the Main Configuration File httpd.conf

Add the following configuration section to Apache's main configuration file, httpd.conf:

<Directory /path/to/myapp>
DirectoryIndex index.php
</Directory>

This method is recommended as best practice by Apache official documentation because it reduces server overhead and avoids the performance penalties associated with .htaccess files. After configuration, restart the Apache service for the changes to take effect.

Configuration Priority and Alternative Approaches

Multiple index files can be specified, and Apache will search for them in order:

DirectoryIndex index.html index.php

This configuration is particularly useful when temporary maintenance pages are needed, allowing quick website state switching by uploading an index.html file.

Real-World Case Analysis

In the referenced case, the website artvietnamgallery.com experienced a similar issue after a server migration. Investigation revealed that although file paths and permissions were correct, server configuration changes prevented index.php from being recognized as the default index file. Such situations are common during hosting provider changes and require revalidation of Apache configurations.

Permissions and Security Considerations

Beyond index file configuration, it is essential to ensure that directories have appropriate read permissions. If the Apache process lacks access to directory contents, a "forbidden" error will occur even with correct configurations. It is recommended to check directory permissions using:

ls -la /path/to/directory

Verification and Testing Methods

After configuration, verify using the following steps:

1. Restart the Apache service: systemctl restart httpd
2. Clear browser cache
3. Access the website root directory to confirm index.php loads automatically
4. Check Apache error logs: /var/log/httpd/error_log

Best Practices Summary

For production environments, prioritize using the httpd.conf configuration method and avoid .htaccess files. Regularly review server configurations, especially after system upgrades or migrations, to ensure all necessary index files are properly configured.