.htaccess Rewrite规则失效，请求排查/index.php跳转至/index?action=login问题

Hey there, let's work through this .htaccess problem together and get your redirect working as expected.

First, let's clear up why your current rule isn't doing what you want:

• Your existing rule is trying to redirect /index/ (a directory path with a trailing slash) to /index.php—which is the opposite direction of your goal.
• The RewriteCond lines you added are meant for handling "pretty URLs" (rewriting non-file/directory requests), which isn't necessary for redirecting an existing file like index.php.

Let's break down the fixes step by step:

1. Make sure .htaccess is actually being loaded #

The #1 reason .htaccess rules fail is that Apache isn't allowed to override directory settings. Here's how to confirm:

• Open your Apache site config file (usually in /etc/apache2/sites-available/your-site.conf or apache2.conf).
• Find the <Directory> block pointing to your website's root folder. Ensure it has AllowOverride All (not None). Example:

  <Directory /var/www/html/>
      Options Indexes FollowSymLinks
      AllowOverride All
      Require all granted
  </Directory>
  

• Restart Apache after making changes: sudo systemctl restart apache2.

Quick test to confirm .htaccess is active: Add a random invalid line (like TestInvalidRule) to your .htaccess. If you get a 500 Internal Server Error when visiting your site, it's working—just delete that line afterward.

2. Use the correct redirect rule #

To redirect /index.php to /index?action=login, use this straightforward rule (no extra conditions needed):

RewriteEngine On
# Redirect index.php to index?action=login
RewriteRule ^index\.php$ /index?action=login [R=302,L]

• ^index\.php$: Explicitly matches the exact request for index.php (the backslash escapes the dot, since dots act as wildcards in regex).
• R=302: Uses a temporary redirect (perfect for testing—switch to R=301 only once you confirm it works, to avoid stubborn browser caching).
• L: Tells Apache to stop processing further rules after this one.

3. Fix browser caching problems #

301 redirects get cached aggressively by browsers. If you tested old rules before, your browser might still be using the old redirect. Test in a private/incognito window, or clear your browser cache to be sure.

4. Check Apache error logs for clues #

If it's still not working, check Apache's error log (usually at /var/log/apache2/error.log). It will show syntax errors in your .htaccess, or confirm if the rewrite module is actually enabled (you can double-check with apache2ctl -M | grep rewrite).

内容的提问来源于stack exchange，提问作者rammanoj