.htaccess删除.html扩展名，并添加斜杠并禁止.html文件

Question

I have a static website with html files and I want to call them without the .html ending and a trailing slash.

For example:

www.test.com/test.html

Should be available under

www.test.com/test/

I managed this with the following .htaccess

Options -Multiviews
RewriteEngine On
RewriteCond %{REQUEST_FILENAME} !-d 
RewriteCond %{REQUEST_FILENAME}\.html -f 
RewriteRule ^([^\.]+)/$ $1.html

But both versions of the url lead to the same page. How can I redirect (without .html) or throw a 404 for the .html version?

www.test.com/test.html

This is the working solution with a trailing slash. Thank you @arkascha!

Options -Multiviews
RewriteEngine On

RewriteCond %{REQUEST_FILENAME} -f
RewriteRule ^/?(.+)\.html$ /$1/ [R=301]

RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_FILENAME}\.html -f
RewriteRule ^([^\.]+)/$ $1.html [END]

Answer 1

Well, add another rule that explicitly redirects requests to URLs with "file name extensions"...

Options -Multiviews
RewriteEngine On

RewriteCond %{REQUEST_FILENAME} -f 
RewriteRule ^/?(.+)\.html$ /$1/ [R=301]

RewriteCond %{REQUEST_FILENAME} !-d 
RewriteCond %{REQUEST_FILENAME}\.html -f 
RewriteRule ^/?([^\.]+)/?$ /$1.html [END]

If the above rule set results in a http status 500 ("server internal error"), then chances are that you operate a very old version of the apache http server. In that case you have to use the L flag instead of the END flag and add an additional condition to the first block:

RewriteEngine On

RewriteCond %{REQUEST_URI} .html$
RewriteCond %{REQUEST_FILENAME} -f
RewriteRule ^/?(.+)\.html$ /$1/ [R=301]

RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_FILENAME}\.html -f
RewriteRule ^/?([^\.]+)/?$ /$1.html [L]

---

And a general hint: you should always prefer to place such rules inside the http servers (virtual) host configuration instead of using dynamic configuration files ( .htaccess style files). Those files are notoriously error prone, hard to debug and they really slow down the server. They are only supported as a last option for situations where you do not have control over the host configuration (read: really cheap hosting service providers) or if you have an application that relies on writing its own rewrite rules (which is an obvious security nightmare).