[转帖]Nginx的超时keeplive_timeout配置详解

Nginx的超时keeplive_timeout配置详解

https://blog.csdn.net/weixin_42350212/article/details/81123932

Nginx 处理的每个请求均有相应的超时设置。如果做好这些超时时间的限定,判定超时后资源被释放,用来处理其他的请求,以此提升 Nginx 的性能。

keepalive_timeout

HTTP 是一种无状态协议,客户端向服务器发送一个 TCP 请求,服务端响应完毕后断开连接。

如果客户端向服务器发送多个请求,每个请求都要建立各自独立的连接以传输数据。

HTTP 有一个 KeepAlive 模式,它告诉 webserver 在处理完一个请求后保持这个 TCP 连接的打开状态。若接收到来自客户端的其它请求,服务端会利用这个未被关闭的连接,而不需要再建立一个连接。

KeepAlive 在一段时间内保持打开状态,它们会在这段时间内占用资源。占用过多就会影响性能。

Nginx 使用 keepalive_timeout 来指定 KeepAlive 的超时时间(timeout)。指定每个 TCP 连接最多可以保持多长时间。Nginx 的默认值是 75 秒,有些浏览器最多只保持 60 秒,所以可以设定为 60 秒。若将它设置为 0,就禁止了 keepalive 连接。


1

2


# 配置段: http, server, location

keepalive_timeout 60s;

client_body_timeout

指定客户端与服务端建立连接后发送 request body 的超时时间。如果客户端在指定时间内没有发送任何内容,Nginx 返回 HTTP 408(Request Timed Out)。


1

2


# 配置段: http, server, location

client_body_timeout 20s;

client_header_timeout

客户端向服务端发送一个完整的 request header 的超时时间。如果客户端在指定时间内没有发送一个完整的 request header,Nginx 返回 HTTP 408(Request Timed Out)。

?


1

2


# 配置段: http, server, location

client_header_timeout 10s;

send_timeout

服务端向客户端传输数据的超时时间。


1

2


# 配置段: http, server, location

send_timeout 30s;

客户度连接nginx超时, 建议5s内

接收客户端header超时, 默认60s, 如果60s内没有收到完整的http包头, 返回408


1

2

3

4

5

6


Syntax: client_header_timeout time;

Default: 

client_header_timeout 60s;

Context:  http, server

Defines a timeout for reading client request header. If a client does not transmit the entire header within this time,

the 408 (Request Time-out) error is returned to the client.

接收客户端body超时, 默认60s, 如果连续的60s内没有收到客户端的1个字节, 返回408


1

2

3

4

5

6

7


Syntax: client_body_timeout time;

Default: 

client_body_timeout 60s;

Context:  http, server, location

Defines a timeout for reading client request body. The timeout is set only for a period between two successive read operations, not for the transmission of the whole request body.

If a client does not transmit anything within this time,

the 408 (Request Time-out) error is returned to the client.

keepalive时间,默认75s,通常keepalive_timeout应该比client_body_timeout大


1

2

3

4

5

6


Syntax: keepalive_timeout timeout [header_timeout];

Default: 

keepalive_timeout 75s;

Context:  http, server, location

The first parameter sets a timeout during which a keep-alive client connection will stay open on the server side. The zero value disables keep-alive client connections.

The optional second parameter sets a value in the “Keep-Alive: timeout=time” response header field. Two parameters may differ.

The “Keep-Alive: timeout=time” header field is recognized by Mozilla and Konqueror. MSIE closes keep-alive connections by itself in about 60 seconds.

可以理解为TCP连接关闭时的SO_LINGER延时设置,默认5s


1

2

3

4

5

6

7


Syntax: lingering_timeout time;

Default: 

lingering_timeout 5s;

Context:  http, server, location

When lingering_close is in effect, this directive specifies the maximum waiting time for more client data to arrive. If data are not received during this time,

the connection is closed. Otherwise, the data are read and ignored, and nginx starts waiting for more data again.

The “wait-read-ignore” cycle is repeated, but no longer than specified by the lingering_time directive.

域名解析超时,默认30s


1

2

3

4

5

6


Syntax: resolver_timeout time;

Default: 

resolver_timeout 30s;

Context:  http, server, location

Sets a timeout for name resolution, for example:

resolver_timeout 5s;

发送数据至客户端超时, 默认60s, 如果连续的60s内客户端没有收到1个字节, 连接关闭


1

2

3

4

5

6


Syntax: send_timeout time;

Default: 

send_timeout 60s;

Context:  http, server, location

Sets a timeout for transmitting a response to the client. The timeout is set only between two successive write operations,

not for the transmission of the whole response. If the client does not receive anything within this time, the connection is closed.

nginx与upstream server的连接超时时间


1

2

3

4

5


Syntax: proxy_connect_timeout time;

Default: 

proxy_connect_timeout 60s;

Context:  http, server, location

Defines a timeout for establishing a connection with a proxied server. It should be noted that this timeout cannot usually exceed 75 seconds.

nginx接收upstream server数据超时, 默认60s, 如果连续的60s内没有收到1个字节, 连接关闭


1

2

3

4

5

6


Syntax: proxy_read_timeout time;

Default: 

proxy_read_timeout 60s;

Context:  http, server, location

Defines a timeout for reading a response from the proxied server. The timeout is set only between two successive read operations,

not for the transmission of the whole response. If the proxied server does not transmit anything within this time, the connection is closed.

nginx发送数据至upstream server超时, 默认60s, 如果连续的60s内没有发送1个字节, 连接关闭


1

2

3

4

5

6


Syntax: proxy_send_timeout time;

Default: 

proxy_send_timeout 60s;

Context:  http, server, location

Sets a timeout for transmitting a request to the proxied server. The timeout is set only between two successive write operations,

not for the transmission of the whole request. If the proxied server does not receive anything within this time, the connection is closed.

原文地址:https://www.cnblogs.com/jinanxiaolaohu/p/10421601.html

时间: 2024-08-04 03:57:30

[转帖]Nginx的超时keeplive_timeout配置详解的相关文章

NGINX源码安装配置详解(./configure),最全解析

NGINX ./configure详解 在"./configure"配置中,"--with"表示启用模块,也就是说这些模块在编译时不会自动构建"--without"表示禁用模块,也就是说这些模块在编译时会自动构建,若你想Nginx轻量级运行,可以去除一些不必要的模块. [[email protected] nginx-1.14.0]# ./configure --help => 查看安装配置项 --help 打印帮助信息. --prefix

学习计划 nginx 中 php的配置详解

本章只看一个刚下载的nginx是如何支持php的 -- location ~ \.php$ { root html; fastcgi_pass 127.0.0.1:9000; fastcgi_index index.php; fastcgi_param SCRIPT_FILENAME /scripts$fastcgi_script_name; include fastcgi_params; } 主要学习这里的配置问题 -- 首先看一下location块,这是一个正则匹配,说明了所有以 .php

nginx正反向代理配置详解

一.nginx正向代理介绍及配置 1.环境介绍 代理服务器系统环境为:centos7.3 nginx代理服务器为:192.168.10.10 测试客户端为局域网内任意windows电脑或Linux电脑 2.正向代理简介 nginx不仅可以做反向代理,还能用作正向代理来进行上网等功能.如果把局域网外的Internet想象成一个巨大的资源库,则局域网中的客户端要访问Internet,则需要通过代理服务器来访问,这种代理服务就称为正向代理(也就是大家常说的,通过正向代理进行上网功能) 3.nginx正

nginx 服务器下载安装配置详解

近段时间用了nginx服务  作为总结写一篇博客 与大家分享:时间关系没有说的太过于详细甚至言语有些凌乱望见谅,有不足之处请斧正. 有这几个问题 与大家探讨一下 1 nginx是个什么东东?2为什吗要用nginx 3 如何用? 首先nginx和apache一样是一个web服务器.apache大家都知道 年代久远 世界第一大服务器.它是一个重量级服务器,不支持高迸发.运行数以万计的迸发访问,会导致apache消耗大量的内存,导致http请求响应效率降低,影响用户的体验. nginx的出现就是为了应

nginx 中 php的配置详解

本章只看一个刚下载的nginx是如何支持php的 -- location ~ \.php$ { root html; fastcgi_pass 127.0.0.1:9000; fastcgi_index index.php; fastcgi_param SCRIPT_FILENAME /scripts$fastcgi_script_name; include fastcgi_params; } 主要学习这里的配置问题 -- 首先看一下location块,这是一个正则匹配,说明了所有以 .php

Nginx + Tomcat 负载均衡配置详解

Nginx作为反向代理服务器,实现负载均衡.首先浏览器发起请求,到达Nginx,由Nginx将请求地址转发给相应的tomcat服务器,再由tomcat服务器将结果返回给Nginx,Nginx将结果再转发给浏览器. 在这过程中,对于浏览器来说,并不知道后端的存在, 相对于Tomact来说,当前的客户端是Nginx服务器.这就完成了一个代理的过程. 首先准备三台Linux服务器:IP地址分别为 192.168.1.61  192.168.1.62  192.168.1.63 其中61安装nginx服

nginx 编译安装与配置详解

一.编译安装 1.使用yum安装所需的包,虽然需要编译几个依赖包,pcre.zlib.openssl yum -y groupinstall "Development Tools""Server Platform Development" yum install pcre-devel zlib-devel openssl-devel gcc* (一般系统装好了,以下的这几个包openssl.zlib.pcre都已经安装上了,注意: pcre-devel zlib-d

Nginx配置文件(nginx.conf)配置详解

Nginx的配置文件nginx.conf配置详解如下: user nginx nginx ; Nginx用户及组:用户 组.window下不指定 worker_processes 8; 工作进程:数目.根据硬件调整,通常等于CPU数量或者2倍于CPU. error_log  logs/error.log; error_log  logs/error.log  notice; error_log  logs/error.log  info; 错误日志:存放路径. pid logs/nginx.pi

nginx的安装配置详解

title: nginx的安装配置详解tags: nginx,虚拟服务器,curl nginx的安装配置详解 1. 介绍各个常用的服务端口 21 ftp :22 ssh:25 smtp:3306 mysql:873 rsync:3389 远程桌面:161 snmp:111 rpcbind:80 www http:443 https:110 pop3:53 dns:514 rsyslog 我们常用的nslookup和dig查询域名解析工具的安装包为bind-utils,如yum install b