Nginx Rewrite Rules common global variables and Detailed

Why 80% of the code can not do farming architect? >>>

Each is very easy to forget Nginx variables listed below to some common

$remote_addr		//获取客户端ip
$binary_remote_addr	//客户端ip（二进制)
$remote_port		//客户端port，如：50472
$remote_user		//已经经过Auth Basic Module验证的用户名
$host			//请求主机头字段，否则为服务器名称，如:blog.sakmon.com
$request		//用户请求信息，如：GET ?a=1&b=2 HTTP/1.1
$request_filename	//当前请求的文件的路径名，由root或alias和URI request组合而成，如：/2013/81.html
$status			//请求的响应状态码,如:200
$body_bytes_sent        // 响应时送出的body字节数数量。即使连接中断，这个数据也是精确的,如：40
$content_length	       // 等于请求行的“Content_Length”的值
$content_type	       // 等于请求行的“Content_Type”的值
$http_referer	       // 引用地址
$http_user_agent      // 客户端agent信息,如：Mozilla/5.0 (Windows NT 5.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/29.0.1547.76 Safari/537.36
$args		     //与$query_string相同 等于当中URL的参数(GET)，如a=1&b=2
$document_uri	     //与$uri相同  这个变量指当前的请求URI，不包括任何参数(见$args) 如:/2013/81.html
$document_root	     //针对当前请求的根路径设置值
$hostname	     //如：centos53.localdomain
$http_cookie	    //客户端cookie信息
$cookie_COOKIE	    //cookie COOKIE变量的值
$is_args	//如果有$args参数，这个变量等于”?”，否则等于”"，空值，如?
$limit_rate	//这个变量可以限制连接速率，0表示不限速
$query_string	    // 与$args相同 等于当中URL的参数(GET)，如a=1&b=2
$request_body	   // 记录POST过来的数据信息
$request_body_file	//客户端请求主体信息的临时文件名
$request_method	      //客户端请求的动作，通常为GET或POST,如：GET
$request_uri	      //包含请求参数的原始URI，不包含主机名，如：/2013/81.html?a=1&b=2
$scheme		       //HTTP方法（如http，https）,如：http
$uri			//这个变量指当前的请求URI，不包括任何参数(见$args) 如:/2013/81.html
$request_completion	//如果请求结束，设置为OK. 当请求未结束或如果该请求不是请求链串的最后一个时，为空(Empty)，如：OK
$server_protocol	//请求使用的协议，通常是HTTP/1.0或HTTP/1.1，如：HTTP/1.1
$server_addr		//服务器IP地址，在完成一次系统调用后可以确定这个值
$server_name		//服务器名称，如：blog.sakmon.com
$server_port		//请求到达服务器的端口号,如：80

Rewrite canonical correlation Detailed instructions:

corresponds to the rewrite of nginx apache RewriteRule (rewrite rules can be the original apache quotes can be used directly in most cases), which can be used in the server, location, and decision block IF condition, the command format is as follows: rewrite regex replacement flag rewrite regex replacement target flag mark

Regular expression matching, there are several special the following wording:

~ Is a case-sensitive match

~ * Is a case-insensitive match

! ~ And! ~ * Do not match are case-insensitive and case-insensitive mismatch

Files and directories matching judgment are the following wording:

-f and! -f used to determine whether a file exists

-d and! -d to determine whether there is a directory

-e and! -e used to determine whether there is a file or directory

-x and! -x is used to determine whether an executable file

flag can be marked in the following formats:

last - basically use this Flag.

break - abort Rewirte, not continue to match

redirect - returns an HTTP redirect temporary state 302

permanent - Returns permanent redirects HTTP status 301

Use last break and realize URI rewrite, the browser address bar unchanged. And both nuances, using alias instruction must last flag; proxy_pass use instructions required break mark. Last flag rewrite rules in the finished article, will have on its host server {......} request to reinitiate the tab, and the break is marked after the completion of this rule matching, matching termination.

Nginx Rewrite such as how 301 Jump: Jump to the 54php.cn www.54php.cn

server {
    listen       80;
    server_name   www.54php.cn  54php.cn;
    if ($host != 'www.54php.cn' ) { 
        rewrite ^/(.*)$ http://www.54php.cn/$1 permanent; 
    } 
}

Set the expiration time depending on the file type:

location ~* \.(js|css|jpg|jpeg|gif|png|swf)$ {
    if (-f $request_filename) {
       expires    1h;
       break;
    }
}

Original Address: Nginx Rewrite rules commonly used global variables and Detailed
Tags: nginx global variable rewrite

Intelligent Recommendation

Reproduced in: https: //my.oschina.net/54php/blog/689342