-1

I am searching for a few hours on how to redirect all .php files to the file without the .php.

I know there is surely a fast answer for this but I have really trouble finding it.

How can I say that if someone loads mysite.com/mysubfolder/mysecondsub/myfile.php goes to mysite.com/mysubfolder/mysecondsub/myfile?

Like a normal rewrite except the URL PHP redirects to the one without the PHP extension.

(using .htaccess if possible and mod_rewrite)

I configured Apache2.conf to allow overwrites so that I am able to use .htacess.

It works when I use something like this post htaccess remove index.php from url

But the thing is that it works if I write mysite.com/url, but if I write mysite.com/url.php it does not redirect to mysite/url (which is what I want) I tried a few solutions but still no idea.

Jason Aller
  • 3,541
  • 28
  • 38
  • 38
Poli
  • 113
  • 14
  • 1
    There are literally _thousands_ of answers for this alone here on SO. What do you expect as an answer to this question? Another answer repeating what has already been written so often and what you already can read? If you want an answer that actually helps you to solve your issue you will need to provide more information. What did you actually try (the code please!), what happend when you tried that (be precise please!), what are other relevant settings inside your environment (how did you make sure your htaccess file is actually considered at all?)... – arkascha Apr 15 '20 at 17:51

1 Answers1

1

This probably is what you are looking for: 

RewriteEngine on

RewriteRule ^/?(.+)\.php$ /$1 [R=301]

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

It is a good idea to start out with a 302 temporary redirection and only change that to a 301 permanent redirection later, once you are certain everything is correctly set up. That prevents caching issues while trying things out...

In case you receive an internal server error (http status 500) using the rule above then chances are that you operate a very old version of the apache http server. You will see a definite hint to an unsupported [END] flag in your http servers error log file in that case. You can either try to upgrade or use the older [L] flag, it probably will work the same in this situation, though that depends a bit on your setup.

This implementation will work likewise in the http servers host configuration or inside a distributed configuration file (".htaccess" file). Obviously the rewriting module needs to be loaded inside the http server and enabled in the http host. In case you use a distributed configuration file you need to take care that it's interpretation is enabled at all in the host configuration and that it is located in the host's DOCUMENT_ROOT folder.

And a general remark: you should always prefer to place such rules in the http servers host configuration instead of using distributed configuration files (".htaccess"). Those distributed configuration files add complexity, are often a cause of unexpected behavior, hard to debug and they really slow down the http server. They are only provided as a last option for situations where you do not have access to the real http servers host configuration (read: really cheap service providers) or for applications insisting on writing their own rules (which is an obvious security nightmare).

arkascha
  • 41,620
  • 7
  • 58
  • 90
  • Fine, good to hear that I could help. And a hint: take care to actually understand the directives, do not just copy something you found on the internet. Everything I posted is already demonstrated on hundreds of answers here on SO and also in the documentation of the rewriting module... – arkascha Apr 17 '20 at 16:21