0

I have this:

website/test.php?id=1

How to get this?

website/test/1

I use this to remove .php extension. I tried a few rules to get the needed result but I couldn't.

RewriteEngine On
RewriteCond %{REQUEST_FILENAME}.php -f
RewriteRule !.*\.php$ %{REQUEST_FILENAME}.php [QSA,L]
Lawrence Cherone
  • 46,049
  • 7
  • 62
  • 106
Vladislav
  • 1
  • 1
    Does this answer your question? Possible duplicate. [Reference: mod\_rewrite, URL rewriting and "pretty links" explained](https://stackoverflow.com/questions/20563772/reference-mod-rewrite-url-rewriting-and-pretty-links-explained) – Lawrence Cherone Oct 30 '19 at 17:53

1 Answers1

0

This should point you into the right direction: 

RewriteEngine On

RewriteCond %{REQUEST_FILENAME}.php -f
RewriteRule !.*\.php$ %{REQUEST_FILENAME}.php [END]

RewriteCond %{REQUEST_URI} ^/([^/]+)/(\d+)/?$
RewriteCond %1.php -f
RewriteRule ^ /%1.php?id=%2 [END]

It checks the path component of the requested URL, looks whether a corresponding php script exists similar to you already existing rewrite rule and if so performs the actual internal rewriting.

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 dynamic 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 dynamic 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 dynamic configuration files (".htaccess"). Those dynamic 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