使用htaccess删除结尾的斜杠，index.php，并仍然使用相对路径

Question

I am trying to write an .htaccess file that accomplishes the following goals:

• Strip trailing slash at the end of all URLS
• Drop the file name for index.php
• Drop the .php extension for everything that isn't the index
• Keep all trailing data in URLs to be processed by index.php
• Use relative URLs, without a link to the site root since the .htaccess only affects a subfolder (/admin as in the examples below)

Some example URLS (display URL = actual location):

• /admin = /admin/index.php
• /admin/pagename = /admin/pagename.php
• /admin/directory = /admin/directory/index.php
• /admin/one/two/three = /admin/index.php where I can parse $_SERVER['REQUEST_URI'] with PHP to get the variables one, two, and three

And here's what I have so far in the folder ABOVE admin. It removes the php extension while allowing me to access any existing files, but it also strips everything after .php and doesn't remove trailing slashes.

RewriteEngine On

# Redirect php filename externally
RewriteCond %{THE_REQUEST} ^[A-Z]{3,}\s([^.]+)\.php [NC]
RewriteRule ^ %1 [R=302,L,QSA]
# change 302 to 301 on live for perm redirect

# Redirect php filename internally
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_FILENAME}.php -f
RewriteRule ^(.*?)/?$ $1.php [L,QSA]

# Rewrite Admin URLS (after specififcally looking for files)
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule admin/. admin/index.php [L,QSA]
# index.php looks at $_SERVER['REQUEST_URI'] to decide what to do next

# No Directory Listings
Options -Indexes

My biggest concern is being able to include files (.php, .inc, .css, .js) with relative paths and not having to use absolute paths if I can help it.

Answer 1

I generally prefer to go with a framework that provides routing capabilities instead of the nightmare of all those Rewrite rules for folders/files. There are a slew of PHP frameworks that support this easily, such as Silex , Symfony , or Laravel , to name a few.

Another reason that doing the routing in the application is easier, is that it abstracts application routing from the webserver for the most part. For example, if you move to Nginx, you will have to refactor all of the above.

My .htaccess might look something like the following:

<IfModule mod_rewrite.c>
    RewriteEngine On
    # Redirect to non-trailing slash
    RewriteRule ^(.*)/$ /$1 [R=301,L]
    # Block access to "hidden" directories whose names begin with a period.
    RewriteRule "(^|/)\." - [F]
    RewriteBase    /
    # Redirect requests that have no real file
    RewriteCond    %{REQUEST_FILENAME}  !-f
    RewriteRule    (.*)  index.php    [QSA,L]
</IfModule>