In-depth analysis of PHP framework routing implementation under Nginx

When all frameworks process business requests, they will process the path part of the URL and assign it to the specified code for processing.
The key to realizing this function is to obtain the data of the URL part in the $_SERVER global variable

When the requested path is
http://test.com/article?id= 1
http://test.com/article/update?id=1

supports the above url mode, no need to configure the passing PATH_INFO variable, and no need to configure pseudo-static removal index.php
The simplest nginx configuration is as follows:

server {
        listen 80; 
        server_name  test.com;
        access_log  /var/log/nginx/test.com.access.log  main;
        root   /home/test;
        index  index.html index.htm index.php;
        location / { 
                try_files $uri $uri/ /index.php?q=$uri&$args;
        }   
        location ~ \.php {
                fastcgi_pass   127.0.0.1:9000;
                fastcgi_index  index.php;
                fastcgi_param  SCRIPT_FILENAME  $document_root$fastcgi_script_name;
                include        fastcgi_params;
        }   
}

There are several key points to pay attention to in this configuration:

1.try_files must be configured in the location block. This can be used to remove index.php. If not configured, you must add /index.php/
2.location ~ \.php
a. Sometimes you will be troubled by whether it ends with $. The key point is to check whether try_files exists. If the try_files directive does not exist, then it must not end with $. In this way, it can still be accessed by using the mode with /index.php/ in the path.
b. If there is a try_files directive, and location ~ \.php$ here ends with $, then /index.php/ cannot be matched in the location of php, but try_files rewrites the parameters to index.php? q= is successful, so it can also be accessed this way.

At this time, in the $_SERVER variable, the variable values ​​that are often used for routing processing by major frameworks or self-written programs are as follows:

$_SERVER["PHP_SELF"]=>"/ index.php", there is no parameter

$_SERVER["PATH_INFO"]=> in the URL, it does not exist at all, because Nginx does not pass this variable

$_SERVER["REQUEST_URI"] =>"/article/update?id=1", this is the key to implementing routing, the parameters all exist

##The more compatible processing in PHP is:

$uri=$_SERVER['REQUEST_URI'];
$uri=str_replace("/index.php","",$uri);
if(strpos($uri,"?")!==false){
   $uri=substr($uri,0,strpos($uri,'?'));
}
$uri=trim($uri,'/');
var_dump($uri);//获取到 article/update

Recommended tutorial:

PHP video tutorial

The above is the detailed content of In-depth analysis of PHP framework routing implementation under Nginx. For more information, please follow other related articles on the PHP Chinese website!