- html - 出于某种原因,IE8 对我的 Sass 文件中继承的 html5 CSS 不友好?
- JMeter 在响应断言中使用 span 标签的问题
- html - 在 :hover and :active? 上具有不同效果的 CSS 动画
- html - 相对于居中的 html 内容固定的 CSS 重复背景?
我想知道是否有一个引用文档说 NGINX 所有变量都可以在 log_format 部分使用。
refer to documentation
我还没有找到这样的文件,允许列出名称、描述和格式(或类型)
提前谢谢
最佳答案
通过 NginX 文档,确实不清楚日志格式指令中可以使用哪些变量。
有些肯定可用:http://nginx.org/en/docs/http/ngx_http_log_module.html#log_format
相同的变量以 (ngx_http_log_module)
出现在这个按字母顺序排列的列表中:http://nginx.org/en/docs/varindex.html
但是默认的combined
中列出的那个格式(如 $remote_addr
)没有出现。它们仍然可用于日志格式指令。
此外,其中两个没有出现在这个按字母顺序排列的列表中:$http_referer
和 $http_user_agent
.我猜这是因为它们是 $http_
的一部分多变的:
$http_name : arbitrary request header field; the last part of a variable 'name' is the field name converted to lower case with dashes replaced by underscores.
$ancient_browser equals the value set by the ancient_browser_value directive, if a browser was identified as ancient
$arg_ argument in the request line
$args arguments in the request line
$binary_remote_addr client address in a binary form, value’s length is always 4 bytes for IPv4 addresses or 16 bytes for IPv6 addresses
$body_bytes_sent number of bytes sent to a client, not counting the response header; this variable is compatible with the “%B” parameter of the mod_log_config Apache module
$bytes_sent number of bytes sent to a client (1.3.8, 1.2.5)
$connection connection serial number (1.3.8, 1.2.5)
$connection_requests current number of requests made through a connection (1.3.8, 1.2.5)
$connections_active same as the Active connections value
$connections_reading same as the Reading value
$connections_waiting same as the Waiting value
$connections_writing same as the Writing value
$content_length “Content-Length” request header field
$content_type “Content-Type” request header field
$cookie_ the named cookie
$date_gmt current time in GMT. The format is set by the config command with the timefmt parameter
$date_local current time in the local time zone. The format is set by the config command with the timefmt parameter
$document_root root or alias directive’s value for the current request
$document_uri same as $uri
$fastcgi_path_info the value of the second capture set by the fastcgi_split_path_info directive. This variable can be used to set the PATH_INFO parameter
$fastcgi_script_name request URI or, if a URI ends with a slash, request URI with an index file name configured by the fastcgi_index directive appended to it. This variable can be used to set the SCRIPT_FILENAME and PATH_TRANSLATED parameters that determine the script name in PHP. For example, for the “/info/” request with the following directives
fastcgi_index index.php;
fastcgi_param SCRIPT_FILENAME /home/www/scripts/php$fastcgi_script_name;
the SCRIPT_FILENAME parameter will be equal to “/home/www/scripts/php/info/index.php”
$geoip_area_code telephone area code (US only)
$geoip_city city name, for example, “Moscow”, “Washington”
$geoip_city_continent_code two-letter continent code, for example, “EU”, “NA”
$geoip_city_country_code two-letter country code, for example, “RU”, “US”
$geoip_city_country_code3 three-letter country code, for example, “RUS”, “USA”
$geoip_city_country_name country name, for example, “Russian Federation”, “United States”
$geoip_country_code two-letter country code, for example, “RU”, “US”
$geoip_country_code3 three-letter country code, for example, “RUS”, “USA”
$geoip_country_name country name, for example, “Russian Federation”, “United States”
$geoip_dma_code DMA region code in US (also known as “metro code”), according to the geotargeting in Google AdWords API
$geoip_latitude latitude
$geoip_longitude longitude
$geoip_org organization name, for example, “The University of Melbourne”
$geoip_postal_code postal code
$geoip_region two-symbol country region code (region, territory, state, province, federal land and the like), for example, “48”, “DC”
$geoip_region_name country region name (region, territory, state, province, federal land and the like), for example, “Moscow City”, “District of Columbia”
$gzip_ratio achieved compression ratio, computed as the ratio between the original and compressed response sizes
$host in this order of precedence: host name from the request line, or host name from the “Host” request header field, or the server name matching a request
$hostname host name
$http2 negotiated protocol identifier: “h2” for HTTP/2 over TLS, “h2c” for HTTP/2 over cleartext TCP, or an empty string otherwise
$http_ arbitrary request header field; the last part of the variable name is the field name converted to lower case with dashes replaced by underscores. Examples: $http_referer, $http_user_agent
$https “on” if connection operates in SSL mode, or an empty string otherwise
$invalid_referer Empty string, if the “Referer” request header field value is considered valid, otherwise “1”
$is_args “?” if a request line has arguments, or an empty string otherwise
$limit_rate setting this variable enables response rate limiting; see limit_rate
$memcached_key Defines a key for obtaining response from a memcached server
$modern_browser equals the value set by the modern_browser_value directive, if a browser was identified as modern
$msec current time in seconds with the milliseconds resolution (1.3.9, 1.2.6)
$msie equals “1” if a browser was identified as MSIE of any version
$nginx_version nginx version
$pid PID of the worker process
$pipe “p” if request was pipelined, “.” otherwise (1.3.12, 1.2.7)
$proxy_add_x_forwarded_for the “X-Forwarded-For” client request header field with the $remote_addr variable appended to it, separated by a comma. If the “X-Forwarded-For” field is not present in the client request header, the $proxy_add_x_forwarded_for variable is equal to the $remote_addr variable
$proxy_host name and port of a proxied server as specified in the proxy_pass directive
$proxy_port port of a proxied server as specified in the proxy_pass directive, or the protocol’s default port
$proxy_protocol_addr client address from the PROXY protocol header, or an empty string otherwise (1.5.12). the PROXY protocol must be previously enabled by setting the proxy_protocol parameter in the listen directive.
$proxy_protocol_port client port from the PROXY protocol header, or an empty string otherwise (1.11.0). the PROXY protocol must be previously enabled by setting the proxy_protocol parameter in the listen directive.
$query_string same as $args
$realip_remote_addr keeps the original client address (1.9.7)
$realip_remote_port keeps the original client port (1.11.0)
$realpath_root an absolute pathname corresponding to the root or alias directive’s value for the current request, with all symbolic links resolved to real paths
$remote_addr client address
$remote_port client port
$remote_user user name supplied with the Basic authentication
$request full original request line
$request_body request bod. The variable’s value is made available in locations processed by the proxy_pass, fastcgi_pass, uwsgi_pass, and scgi_pass directives.
$request_body_file name of a temporary file with the request body. At the end of processing, the file needs to be removed. To always write the request body to a file, client_body_in_file_only needs to be enabled. When the name of a temporary file is passed in a proxied request or in a request to a FastCGI/uwsgi/SCGI server, passing the request body should be disabled by the proxy_pass_request_body off, fastcgi_pass_request_body off, uwsgi_pass_request_body off, or scgi_pass_request_body off directives, respectively.
$request_completion “OK” if a request has completed, or an empty string otherwise
$request_filename file path for the current request, based on the root or alias directives, and the request URI
$request_id unique request identifier generated from 16 random bytes, in hexadecimal (1.11.0)
$request_length request length (including request line, header, and request body) (1.3.12, 1.2.7)
$request_method request method, usually “GET” or “POST”
$request_time request processing time in seconds with a milliseconds resolution (1.3.9, 1.2.6); time elapsed since the first bytes were read from the client
$request_uri full original request URI (with arguments)
$scheme request scheme, “http” or “https”
$secure_link The status of a link check. The specific value depends on the selected operation mode
$secure_link_expires The lifetime of a link passed in a request; intended to be used only in the secure_link_md5 directive
$sent_http_ arbitrary response header field; the last part of the variable name is the field name converted to lower case with dashes replaced by underscores
$server_addr an address of the server which accepted a request. Computing a value of this variable usually requires one system call. To avoid a system call, the listen directives must specify addresses and use the bind parameter.
$server_name name of the server which accepted a request
$server_port port of the server which accepted a request
$server_protocol request protocol, usually “HTTP/1.0”, “HTTP/1.1”, or “HTTP/2.0”
$session_log_binary_id current session ID in binary form (16 bytes)
$session_log_id current session ID
$slice_range the current slice range in HTTP byte range format, for example, bytes=0-1048575
$spdy SPDY protocol version for SPDY connections, or an empty string otherwise
$spdy_request_priority request priority for SPDY connections, or an empty string otherwise
$ssl_cipher returns the string of ciphers used for an established SSL connection
$ssl_client_cert returns the client certificate in the PEM format for an established SSL connection, with each line except the first prepended with the tab character; this is intended for the use in the proxy_set_header directive
$ssl_client_fingerprint returns the SHA1 fingerprint of the client certificate for an established SSL connection (1.7.1)
$ssl_client_i_dn returns the “issuer DN” string of the client certificate for an established SSL connection
$ssl_client_raw_cert returns the client certificate in the PEM format for an established SSL connection
$ssl_client_s_dn returns the “subject DN” string of the client certificate for an established SSL connection
$ssl_client_serial returns the serial number of the client certificate for an established SSL connection
$ssl_client_verify returns the result of client certificate verification: “SUCCESS”, “FAILED”, and “NONE” if a certificate was not present
$ssl_protocol returns the protocol of an established SSL connection
$ssl_server_name returns the server name requested through SNI (1.7.0)
$ssl_session_id returns the session identifier of an established SSL connection
$ssl_session_reused returns “r” if an SSL session was reused, or “.” otherwise (1.5.11)
$status response status (1.3.2, 1.2.2)
$tcpinfo_rtt,
$tcpinfo_rttvar,
$tcpinfo_snd_cwnd,
$tcpinfo_rcv_space information about the client TCP connection; available on systems that support the TCP_INFO socket option
$time_iso8601 local time in the ISO 8601 standard format (1.3.12, 1.2.7)
$time_local local time in the Common Log Format (1.3.12, 1.2.7)
$uid_got The cookie name and received client identifier
$uid_reset If the variable is set to a non-empty string that is not “0”, the client identifiers are reset. The special value “log” additionally leads to the output of messages about the reset identifiers to the error_log
$uid_set The cookie name and sent client identifier
$upstream_addr keeps the IP address and port, or the path to the UNIX-domain socket of the upstream server. If several servers were contacted during request processing, their addresses are separated by commas, e.g. “192.168.1.1:80, 192.168.1.2:80, unix:/tmp/sock”. If an internal redirect from one server group to another happens, initiated by “X-Accel-Redirect” or error_page, then the server addresses from different groups are separated by colons, e.g. “192.168.1.1:80, 192.168.1.2:80, unix:/tmp/sock : 192.168.10.1:80, 192.168.10.2:80”
$upstream_cache_status keeps the status of accessing a response cache (0.8.3). The status can be either “MISS”, “BYPASS”, “EXPIRED”, “STALE”, “UPDATING”, “REVALIDATED”, or “HIT”
$upstream_connect_time time spent on establishing a connection with an upstream server
$upstream_cookie_ cookie with the specified name sent by the upstream server in the “Set-Cookie” response header field (1.7.1). Only the cookies from the response of the last server are saved
$upstream_header_time time between establishing a connection and receiving the first byte of the response header from the upstream server
$upstream_http_ keep server response header fields. For example, the “Server” response header field is available through the $upstream_http_server variable. The rules of converting header field names to variable names are the same as for the variables that start with the “$http_” prefix. Only the header fields from the response of the last server are saved
$upstream_response_length keeps the length of the response obtained from the upstream server (0.7.27); the length is kept in bytes. Lengths of several responses are separated by commas and colons like addresses in the $upstream_addr variable
$upstream_response_time time between establishing a connection and receiving the last byte of the response body from the upstream server
$upstream_status keeps status code of the response obtained from the upstream server. Status codes of several responses are separated by commas and colons like addresses in the $upstream_addr variable
$uri current URI in request, normalized. The value of $uri may change during request processing, e.g. when doing internal redirects, or when using index files.
关于logging - 日志格式的字典变量 NGINX,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/37437153/
我只想国家和资本化的值(value)。 这是我的完整代码: cities = { 'rotterdam': { 'country': 'netherlands',
想更好地了解如何比较对象类型的键。 dicOverall.exists(dic2) 返回 False,而 dicOverall.exists(dic1) 返回 True。我不太确定 .Exists 如
我是编程和 python 的新手,我不知道如何解决这个问题。 my_dict = {'tiger': ['claws', 'sharp teeth', 'four legs', 'stripes'
这个问题已经有答案了: Accessing an object property with a dynamically-computed name (19 个回答) 已关闭 8 年前。 我引用了这篇文
希望有人能帮忙。我正在使用 Python,我希望能够执行以下操作。 我有一组对象(例如形状)和一系列作用于这些对象的命令。命令的格式为命令字符串,后跟可变数量的参数,可以是字符串或整数 例如形状“矩形
我在文件中保存了一本字典。我从 python 交互式 shell 将字典加载到内存中,我的系统监视器显示 python 进程消耗了 4GB。以下命令提供以下输出: size1 = sys.getsiz
如果我运行以下代码: import json foo = [ { "name": "Bob", "occupation": "", "stand
我尝试获取列名及其索引,并将结果保存为数据框或字典: df <- data.frame(a=rnorm(10), b=rnorm(10), c=rnorm(10)) 我该怎么做?谢谢。 column
我正在尝试获取输入,如果字典 logins 有一个与我的输入匹配的键,我想返回该键的值。 logins = { 'admin':'admin', 'turtle':'password1
在 Perl 世界中有一个很棒的东西叫做 CPAN .它是开源 Perl 库的大型存储。 我使用来自 CPAN 的模块,我已经发布了 several distributions myself . 我使
这个问题已经有答案了: Is there a Python dict without values? (3 个回答) 已关闭 3 年前。 我有一个问题,我想跟踪大量值。如果我从未遇到过该值,我将执行操
想知道这是否可能。 我们有一个第 3 方库,其中包含有关用户的识别信息... 与库的主要交互是通过一个以字符串为键的 HashTable,并返回该键的信息对象图。 问题是, key 显然是区分大小写的
我是 .NET 编程的新手。对不起,如果这个问题以前被问过。 我目前正在学习 F#。 Dictionary、Hashtable 和 Map 之间有什么区别?我应该什么时候使用? 我还有一个标题中没有提
我正在尝试使用SVM进行3类分类。为此,我正在SVM培训期间准备词汇表。但是,由于我在SVM预测期间获得随机结果,因此我怀疑我的词汇创建方法中存在一些问题。我创建词汇的代码如下: //Mat trai
就目前情况而言,这个问题不太适合我们的问答形式。我们希望答案得到事实、引用资料或专业知识的支持,但这个问题可能会引发辩论、争论、民意调查或扩展讨论。如果您觉得这个问题可以改进并可能重新开放,visit
假设我有一个以下形式的嵌套字典: {'geo': {'bgcolor': 'white','lakecolor': 'white','caxis': {'gridcolor': 'white', 'l
我有一个 java 应用程序,每秒启动和停止数亿个项目(从外部脚本调用)多次。 Input: String key Output: int value 此应用程序的目的是在从未永远改变的Map(约30
我正在尝试找出字典与集合和数组相比的相对优势和功能。 我发现了一篇很棒的文章here但找不到一个简单的表格来比较所有不同的功能。 有人知道吗? 最佳答案 请参阅下表,对集合和字典进行有用的比较。 (该
我想要一个字典,它可以为字典中没有的任何键返回一个指定的值,例如: var dict = new DictWithDefValues("not specified"); dict.Add("bob78
我是 python 新手,目前仍在学习如何处理列表和字典。 我有这两个功能 def food_database(item_name, size_serv, calorie_serv, prot
我是一名优秀的程序员,十分优秀!