客戶度連線nginx超時, 建議5s內

接收客戶端header超時, 預設60s, 如果60s內沒有收到完整的http包頭, 返回408

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

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大

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

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

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個位元組, 連線關閉

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的連線超時時間

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個位元組, 連線關閉

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個位元組, 連線關閉

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.

轉自：https://blog.csdn.net/xizaihui/article/details/53306496?utm_source=itdadao&utm_medium=referral

另參考：https://blog.csdn.net/achenyuan/article/details/79122894