时间:2021-05-19
Variables
The core module supports built-in variables, whose names correspond with the names of variables in Apache.
First of all, there are the variables, which represent the lines of the title of the client request, for example, $http_user_agent, $http_cookie, and so forth.
Furthermore, there are other variables:
Edit section: $arg_PARAMETER $arg_PARAMETER
This variable contains the value of the GET request variable PARAMETER if present in the query string
Edit section: $args $args
This variable is equal to arguments in the line of request;
Edit section: $binary_remote_addr $binary_remote_addr
The address of the client in binary form;
Edit section: $body_bytes_sent $body_bytes_sent
(undocumented)
Edit section: $content_length $content_length
This variable is equal to line Content-Length in the header of request;
Edit section: $content_type $content_type
This variable is equal to line Content-Type in the header of request;
Edit section: $cookie_COOKIE $cookie_COOKIE
The value of the cookie COOKIE;
Edit section: $document_root $document_root
This variable is equal to the value of directive root for the current request;
Edit section: $document_uri $document_uri
The same as $uri.
Edit section: $host $host
This variable is equal to line Host in the header of request or name of the server processing the request if the Host header is not available.
This variable may have a different value from $http_host when the Host input header is absent or has an empty value.
Edit section: $http_HEADER $http_HEADER
The value of the HTTP header HEADER when converted to lowercase and with ‘dashes' converted to ‘underscores', e.g. $http_user_agent, $http_referer…;
Edit section: $is_args $is_args
Evaluates to “?” if $args is set, “” otherwise.
Edit section: $limit_rate $limit_rate
This variable allows limiting the connection rate.
Edit section: $query_string $query_string
The same as $args.
Edit section: $remote_addr $remote_addr
The address of the client.
Edit section: $remote_port $remote_port
The port of the client;
Edit section: $remote_user $remote_user
This variable is equal to the name of user, authenticated by the Auth Basic Module;
Edit section: $request_filename $request_filename
This variable is equal to path to the file for the current request, formed from directives root or alias and URI request;
Edit section: $request_body $request_body
This variable(0.7.58+) contains the body of the request. The significance of this variable appears in locations with directives proxy_pass or fastcgi_pass.
Edit section: $request_body_file $request_body_file
Client request body temporary filename;
Edit section: $request_completion $request_completion
(undocumented)
Edit section: $request_method $request_method
This variable is equal to the method of request, usually GET or POST.
Before and including 0.8.20, this variable always evaluates to the method name of the main request, not the current request if the current request is a subrequest.
Edit section: $request_uri $request_uri
This variable is equal to the complete initial URI together with the arguments;
Edit section: $scheme $scheme
The HTTP scheme (i.e. http, https). Evaluated only on demand, for example:
rewrite ^(.+)$ $scheme://example.com$1 redirect;
Edit section: $server_addr $server_addr
Equal to the server address. As a rule, for obtaining the value of this variable is done one system call. In order to avoid system call, it is necessary to indicate addresses in directives listen and to use parameter bind.
Edit section: $server_name $server_name
The name of the server.
Edit section: $server_port $server_port
This variable is equal to the port of the server, to which the request arrived;
Edit section: $server_protocol $server_protocol
This variable is equal to the protocol of request, usually this HTTP/1.0 or HTTP/1.1.
Edit section: $uri $uri
This variable is equal to current URI in the request, it can differ from initial, for example by internal redirects, or with the use of index it is file with internal redirects.
参考:
http://.cn/entry/Nginx-Location%E5%9F%BA%E6%9C%AC%E8%AF%AD%E6%B3%95
http://wiki.nginx.org/NginxHttpCoreModule#Variables
$args 此变量与请求行中的参数相等
$content_length 等于请求行的“Content_Length”的值。
$content_type 等同与请求头部的”Content_Type”的值
$document_root 等同于当前请求的root指令指定的值
$document_uri 与$uri一样
$host 与请求头部中“Host”行指定的值或是request到达的server的名字(没有Host行)一样
$limit_rate 允许限制的连接速率
$request_method 等同于request的method,通常是“GET”或“POST”
$remote_addr 客户端ip
$remote_port 客户端port
$remote_user 等同于用户名,由ngx_http_auth_basic_module认证
$request_filename 当前请求的文件的路径名,由root或alias和URI request组合而成
$request_body_file
$request_uri 含有参数的完整的初始URI
$query_string 与$args一样
$server_protocol 等同于request的协议,使用“HTTP/1.0”或“HTTP/1.1”
$server_addr request到达的server的ip,一般获得此变量的值的目的是进行系统调用。为了避免系统调用,有必要在listen指令中指明ip,并使用bind参数。
$server_name 请求到达的服务器名
$server_port 请求到达的服务器的端口号
$uri 等同于当前request中的URI,可不同于初始值,例如内部重定向时或使用index
声明:本页内容来源网络,仅供用户参考;我单位不保证亦不表示资料全面及准确无误,也不保证亦不表示这些资料为最新信息,如因任何原因,本网内容或者用户因倚赖本网内容造成任何损失或损害,我单位将不会负任何法律责任。如涉及版权问题,请提交至online#300.cn邮箱联系删除。
Lua将其所有的全局变量保存在一个常规的table中,这个table被称为“环境”。它被保存在全局变量_G中。1.全局变量声明:Lua中的全局变量不需要声明就可
Ruby全局变量全局变量以$开头。未初始化的全局变量的值为nil,在使用-w选项后,会产生警告。给全局变量赋值会改变全局状态,所以不建议使用全局变量。下面的实例
局部变量(Localvariables)与全局变量:在子程序或代码块中定义的变量称为局部变量,在程序的一开始定义的变量称为全局变量。全局变量作用域是整个程序,局
Python多进程默认不能共享全局变量主进程与子进程是并发执行的,进程之间默认是不能共享全局变量的(子进程不能改变主进程中全局变量的值)。如果要共享全局变量需要
PHP中变量的作用域可以分为:超全局(全局变量的特殊类型,在局部范围里可直接使用),全局,局部,静态(是局部变量的特殊类型)在PHP中,全局变量实际上是静态全局