.htaccess-将/path.php重写为/ path /，而不是对子目录中的文件进行404处理

Question

Firstly, I apologise. This topic has been rehashed repeatedly, (I know. I read them.) But for whatever reason, my case is either odd, or I'm breaking something else in the .htaccess.

Objective

1. Hide PHP file extensions,
2. 301 any attempt at getting to them to their masquerading path,
3. Allow PHP files within sub-directories to be actually referenced,
4. Rewrite underscores in file names as slashes (/) so they appear to be nested. ( edit: or translate / in the URL to be _'s in the file - unless the directory exists.)

... 3 & 4 are the kickers.

The following code is the .htaccess I've been using prior to this...

<IfModule mod_negotiation.c>
Options -MultiViews
</IfModule>

<IfModule mod_rewrite.c>
RewriteEngine on
RewriteBase /

## Imagine Some Code here ##

# Redirect to domain with www.
RewriteCond %{HTTPS} off
RewriteCond %{HTTP_HOST} !^www\. [NC]
RewriteRule .* http://www.%{HTTP_HOST}%{REQUEST_URI} [R=301,L]
# Same for HTTPS:
RewriteCond %{HTTPS} on
RewriteCond %{HTTP_HOST} !^www\. [NC]
RewriteRule .* https://www.%{HTTP_HOST}%{REQUEST_URI} [R=301,L]

# Ensure all directory URLs have a trailing slash.
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_URI} !\/$
RewriteCond %{REQUEST_URI} !\/[^\/]*\.[^\/]+$
RewriteRule .* http://%{HTTP_HOST}%{REQUEST_URI}/ [L,R=301]
# Same for HTTPS:
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_URI} !\/$
RewriteCond %{REQUEST_URI} !\/[^\/]*\.[^\/]+$
RewriteRule .* https://%{HTTP_HOST}%{REQUEST_URI}/ [L,R=301]
</IfModule>

I have tried adding the following snippets where I noted.

RewriteRule    ^$    /index.php    [L]
RewriteRule    ^([a-zA-Z0-9\-\_/]*)/$    /$1/index.php    [L]
RewriteRule    ^([a-zA-Z0-9\-\_/]*)\.(html|htm)$    /$1.php    [L]
RewriteRule    ^([a-zA-Z0-9\-\_/]*)$    /$1.php    [L]

and

RewriteCond %{REQUEST_FILENAME} !-f
RewriteRule ^([^\.]+)$ $1.php [NC,L]

and the most success was:

# Unless directory, remove trailing slash
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^([^/]+)/$ https://www.actual_domain.com.au/$1 [R=301,L]

# Redirect external .php requests to extensionless url
RewriteCond %{THE_REQUEST} ^(.+)\.php([#?][^\ ]*)?\ HTTP/
RewriteRule ^(.+)\.php$ https://www.actual_domain.com.au/$1 [R=301,L]

# Resolve .php file for extensionless php urls
RewriteRule ^([^/.]+)$ $1.php [L]

That last one was pretty good actually, however, I couldn't access php files at all in any format (with/without extension) in sub-directories. And all attempts at adding in something that handled requirement 4 just didn't work.

As much as I would love for someone to just go BAM, done. Use and enjoy. I would really like to understand what is going wrong too.

Thanks in advance.

-- edit --

As requested by misorude, the following URLs are examples.

URL: actual_domain.com.au/blog - Reads file: /blog.php

URL: actual_domain.com.au/path/to-file - Reads file: /path_to-file.php

URL: actual_domain.com.au/dir/file - Reads file: /dir/file.php

With the last example (/dir/) the dir directory exists. With the /path/ one, it isn't a directory.

Now, as for my wording for objective 3, I have found that the .htaccess code that I have tried appears to prevent anything physically in a sub-directory returns 404. (case in point, that last example above referencing /dir/)

And lastly, with respect to the rewriting of / or _, the file contains the _ and I'd like it to present as a / in the url.

-- edit --

I've managed to do this:

# external redirect from actual URL to pretty one
RewriteCond %{REQUEST_URI} path_to-file\.php [NC]
RewriteRule ^ /path/to-file [R=302,L,NE]

# internal forward from pretty URL to actual one
RewriteRule ^path/to-file/?$ /path_to-file.php [L,NC]

... which works checking the headers, but 404's in practice. It is also hard coding a specific path. Which isn't really what I wanted to do.

Now, the failing in practice. Using: https://www.webconfs.com/http-header-check.php with the url: https://actual_domain.com.au/path/to-file

I get this:

HTTP/1.0 404 Not Found =>
Cache-Control => private, no-cache, no-store, must-revalidate, max-age=0
Pragma => no-cache
Content-Type => text/html
Content-Length => 618
Date => Mon, 12 Aug 2019 06:27:16 GMT
Server => LiteSpeed
Location => https://actual_domain.com.au/path_to-file.php
Alt-Svc => quic=":443"; ma=2592000; v="35,39,43,44"
Connection => close

You can see that the location redirection works, but it still gives 404 - even though going to the redirected path works! :(

Thoughts?

Answer 1

You may have your .htaccess as this:

# turn directory slash on
DirectorySlash On
RewriteEngine On

# add www to a domain name taking care of both http and https
RewriteCond %{HTTP_HOST} !^www\. [NC]
RewriteCond %{HTTPS}s on(s)|
RewriteRule ^ http%1://www.%{HTTP_HOST}%{REQUEST_URI} [R=301,L,NE]

# remove .php from URLs
RewriteCond %{THE_REQUEST} \s/+(.+?)\.php[\s?] [NC]
RewriteRule ^ /%1 [R=301,NE,L]

# ignore all files and directories
RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^ - [L]

# add .php extension
# RewriteCond %{REQUEST_FILENAME}.php -f
RewriteRule ^([^.]+?)/?$ $1.php [L]

# Replace / by _ recursively
RewriteRule ^([^/]+)/(.+)$ $1_$2

Make sure when you test, you only have these rules and you test from a new browser to avoid old cache.