Nginx rewrite like apache?

Earlier, the website works on Apache, and there was a path:
example.org/index (the request went to example.org/index.php)
example.org/admin (the request went to example.org/admin.php)
example.org/profile (the request went to example.org/profile.php)
Apache will automatically process the data path, and quietly opened.
After moving to Nginx, the path of such a plan is not acceptable for him, and climb to finish anywhere *.php - dreary and unreal.
How can I force Nginx to do the same as it did out of the box with Apache rewrite is enabled?
July 4th 19 at 22:58
3 answers
July 4th 19 at 23:02
Maybe you can help https://winginx.com/ru/htaccess if the rules are not tricky
the fact of the matter is that the draft does not exist htaccess file, apache is all done out of the box - lambert_Lynch commented on July 4th 19 at 23:05
July 4th 19 at 23:04
Not sure, but maybe something like this will help:
location / {
 try_files $uri $uri.php /index.php$is_args$args;
}
It is not exactly going to help. Here, any request is redirected to index - lambert_Lynch commented on July 4th 19 at 23:07
: it seems the logic is this:
try by turn uri, then uri.php and only then yeah throw on the index, i.e. index.php leave 404ые, sometimes not so good. In response there is a link to an example, the more correct:

location / {
try_files $uri $uri.php $uri/;
} - osvaldo83 commented on July 4th 19 at 23:10

Find more questions by tags ApacheNginxProcessing URL