Skip to main content

Understanding and Using the .htaccess File

Introduction​

The .htaccess file is a crucial configuration file used by web servers running Apache or LiteSpeed. On our platform, which utilizes the LiteSpeed Web Server, the .htaccess file allows you to manage various settings, such as URL redirection, access control, and much more, directly from your website's root directory.

Where is the .htaccess File Used?​

The .htaccess file is typically found in the root directory of your website, but it can also be placed in any subdirectory. The configurations set in this file apply to the directory it is in and all subdirectories, making it a powerful tool for managing site behavior at different levels.

important

The .htaccess file must be present inside the root folder of your domain for it to work properly. The document root for your domain name is typically located here: File Manager > ./domains/yourdomain.com/public_html.

How is the .htaccess File Used?​

The .htaccess file is used to control server settings on a per-directory basis. Common uses include:

  • URL Redirection: Redirecting visitors from one URL to another.
  • Access Control: Restricting access to specific files or directories.
  • Rewrite Rules: Modifying URL structures to be more user-friendly (SEO-friendly URLs).
  • Error Handling: Customizing error pages (e.g., 404 pages).

Automatically Generated .htaccess​

When you install any CMS (e.g., WordPress, Joomla, Drupal) from our Advanced Installer Hub, the .htaccess file is automatically generated with the default configuration for that CMS. It’s essential to be cautious when modifying this file, as incorrect changes can affect the functionality of your site.

Working with PHP Flags and Values​

The .htaccess file also allows you to set or modify PHP configurations directly. While our Web Control Panel provides a PHP Selector and various PHP options, not all configurations are available there. You can add or modify extra PHP values using .htaccess.

Example PHP Settings​

Here are some examples of how to work with PHP flags and values in the .htaccess file:

  1. Increase Maximum File Upload Size:

    php_value upload_max_filesize 64M
    php_value post_max_size 64M

  2. Set the Maximum Execution Time for Scripts:

    php_value max_execution_time 300

  3. Change the Default Memory Limit:

    php_value memory_limit 256M

  4. Disable Displaying Errors:

    php_flag display_errors Off

  5. Enable Error Logging:

    php_flag log_errors On
    php_value error_log /path/to/your/error_log

  6. Modify Timezone Settings:

    php_value date.timezone "America/New_York"

Important Notes​

  • php_value is used to set a PHP configuration value, while php_flag is used to turn a setting on or off.
  • Be cautious when setting these values, as incorrect settings can cause your site to behave unexpectedly.
  • Always test changes in a staging environment before applying them to your live site.

Examples of Configuration​

Incorrect Configuration​

Here is an example of an incorrect .htaccess configuration that could cause issues:

RewriteEngine On
RewriteRule ^index.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteRule . /index.php [L]

Issue: This configuration will redirect all requests to index.php, even if the file exists, causing an infinite loop.

Correct Configuration​

Here’s how you can correctly write the same configuration:

RewriteEngine On
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]

Explanation: This configuration checks if the requested file or directory exists before redirecting to index.php, preventing an infinite loop.

Additional Rewrite Rule Examples​

Here are some common rewrite rule examples you can use:

  1. Redirect all HTTP requests to HTTPS:

    RewriteEngine On
    RewriteCond %{HTTPS} off
    RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

  2. Remove 'www' from URLs:

    RewriteEngine On
    RewriteCond %{HTTP_HOST} ^www\.(.*)$ [NC]
    RewriteRule ^(.*)$ https://%1/$1 [L,R=301]

  3. Redirect to a maintenance page:

    RewriteEngine On
    RewriteCond %{REMOTE_ADDR} !^123\.456\.789\.000$
    RewriteRule ^(.*)$ /maintenance.html [R=302,L]

Best Practices​

  • Backup Regularly: Always backup your .htaccess file before making changes.
  • Test Changes: After editing, test your changes in a staging environment first.
  • Use Comments: Comment your rules to easily understand them later.
# Redirect from old-page.html to new-page.html
RewriteRule ^old-page.html$ /new-page.html [R=301,L]
  • Limit Access: Restrict access to sensitive files.
<Files ".htaccess">
  Require all denied
</Files>

Warnings and Important Considerations​

What Happens if You Mess Up?​

If the .htaccess file is incorrectly configured or deleted, your website could experience various issues, including:

  • Site Downtime: Incorrect rules might break the site, causing downtime.
  • SEO Impact: Misconfigurations could result in broken URLs, negatively affecting SEO.
  • Access Problems: Improper access rules could lock you or your users out of important parts of the site.

In most cases, you can recover by restoring a backup of the .htaccess file or regenerating it through your CMS.

note

If you accidentally delete the .htaccess file, the website might stop working correctly, especially if you’re using a CMS. Always make sure to regenerate the file if needed.

Final Thoughts​

The .htaccess file is a powerful tool for managing your website's behavior and access. However, it requires careful handling. Use the provided best practices to manage it effectively, and remember that this file is automatically generated when you install any CMS from our Advanced Installer Hub. If you’re unsure about any changes, don’t hesitate to contact the WebHostMost Support Team.

tip

For more detailed configurations and examples, refer to the official LiteSpeed or Apache documentation.