Question posted in
Some documentation to get you started can be found here.

$_GET variables empty .htaccess rewrite – Apache

https://website.com/api/somefolder/test/512/31

Should rewrite to:
https://website.com/api/somefolder/test.php?param1=512&param2=31

and

https://website.com/api/somefolder/anotherfolder/hello/yo/44

Should rewrite to:
https://website.com/api/somefolder/anotherfolder/hello.php?param1=yo&param2=44

RewriteEngine On

RewriteCond %{REQUEST_FILENAME}.php -f
RewriteRule !.*.php$ %{REQUEST_FILENAME}.php?param1=$1&param2=$2 [QSA,L]

The rewrite works but $1 and $2 are empty. Any idea why?

My htaccess file is located in the api directory.

Tags:

2

Answers


  1. 0

    Sure, the two parameters are empty since you never full them with content…

    Take a look at that example instead: 

    RewriteEngine On
RewriteCond %{REQUEST_URI} ^(.+)/(d+)/(d+)$
RewriteCond %1.php -f
RewriteRule ^ %1.php?param1=%2&param2=%3 [QSA,END]

    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).

    Login or Signup to reply.
  2. 0

    You may use this rule in api/.htaccess with Options -MultiViews at the top that turns off content negotiation service of Apache:

    Options -MultiViews
RewriteEngine On
RewriteBase /api/

RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.+?)/([^/]+)/([^/]+)/?$ $1.php?param1=$2&param2=$3 [QSA,NC,L]
    Login or Signup to reply.
Please signup or login to give your own answer.

Back To Top
Search