如何移除网页的.php/.html扩展名且兼容同名目录？

Hey there! I’ve run into this exact issue before—having a file like home.php and a directory named home can throw off your rewrite rules because Apache defaults to prioritizing directories over files. Let’s fix this with targeted .htaccess rules that do exactly what you need: remove .php/.html extensions, and let you control whether files or directories take priority.

Core Solution: Prioritize Files Over Directories #

Here’s a set of rules that will first check for matching .php/.html files (even if a同名 directory exists), then fall back to directories only if no matching files are found.

# Enable rewrite engine
RewriteEngine On

# External Redirect: Strip .php/.html from visible URLs (SEO-friendly)
# e.g., converts example.com/home.php to example.com/home
RewriteCond %{THE_REQUEST} \s/+(.*?)\.(php|html)(\?.*)?\s [NC]
RewriteRule ^ /%1 [R=302,L,NE]

# Internal Rewrite: First try to load the matching .php file
# Works even if a directory with the same name exists
RewriteCond %{REQUEST_FILENAME}.php -f
RewriteRule ^(.*)$ $1.php [L]

# If no .php exists, try matching .html file
RewriteCond %{REQUEST_FILENAME}.html -f
RewriteRule ^(.*)$ $1.html [L]

# Final fallback: If no matching files, serve the directory (if it exists)
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^ - [L]

Breakdown of Each Rule #

• RewriteEngine On: Turns on Apache’s mod_rewrite functionality (make sure this module is enabled on your server!).
• External Redirect: This handles cases where users (or search engines) visit the URL with the extension. It sends a temporary 302 redirect to the clean URL—switch to R=301 once you’ve tested everything to make it permanent (better for SEO). The NE flag preserves any query parameters, so home.php?id=5 becomes home?id=5.
• Internal .php Rewrite: Checks if a .php file exists with the same name as the requested path. If it does, Apache silently loads that file without changing the visible URL. This bypasses directory checks entirely if the file exists.
• Internal .html Rewrite: Same logic as above, but for .html files—runs only if no matching .php file was found.
• Directory Fallback: If neither a .php nor .html file exists, Apache will serve the directory as normal (if it exists).

If You Want to Prioritize Directories Instead #

If you’d rather have directories take precedence over files (e.g., example.com/home loads the home directory instead of home.php), adjust the rules to check for directories first:

RewriteEngine On

# External Redirect (same as before)
RewriteCond %{THE_REQUEST} \s/+(.*?)\.(php|html)(\?.*)?\s [NC]
RewriteRule ^ /%1 [R=302,L,NE]

# First check if the requested path is a directory—serve it if so
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^ - [L]

# Then try .php files
RewriteCond %{REQUEST_FILENAME}.php -f
RewriteRule ^(.*)$ $1.php [L]

# Then try .html files
RewriteCond %{REQUEST_FILENAME}.html -f
RewriteRule ^(.*)$ $1.html [L]

Key Notes to Avoid Issues #

1. Check mod_rewrite: Ensure your Apache server has the mod_rewrite module enabled. You can usually confirm this via your hosting control panel or by running a2enmod rewrite on a local/server terminal.
2. AllowOverride Settings: Make sure your Apache site configuration has AllowOverride All set for your website’s root directory—this lets .htaccess files override default server rules.
3. Test with 302 First: Use R=302 (temporary redirect) while testing to avoid browser caching issues. Once everything works as expected, switch to R=301 for permanent redirects.

Give these rules a shot—they should resolve the conflict between your files and directories while cleaning up your URLs perfectly!

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