具體參數解釋
Nginx 處理的每個請求均有相應的超時設置。如果做好這些超時時間的限定，判定超時后資源被釋放，用來處理其他的請求，以此提升 Nginx 的性能。
HTTP 是一種無狀態協議，客戶端向服務器發送一個 TCP 請求，服務端響應完畢后斷開連接。如果客戶端向服務器發送多個請求，每個請求都要建立各自獨立的連接以傳輸數據。
HTTP 有一個 KeepAlive 模式，它告訴 webserver 在處理完一個請求后保持這個 TCP 連接的打開狀態。若接收到來自客戶端的其它請求，服務端會利用這個未被關閉的連接，而不需要再建立一個連接。
KeepAlive 在一段時間內保持打開狀態，它們會在這段時間內占用資源。占用過多就會影響性能。
Nginx 使用 keepalive_timeout 來指定 KeepAlive 的超時時間（timeout）。指定每個 TCP 連接最多可以保持多長時間。Nginx 的默認值是 75 秒，有些瀏覽器最多只保持 60 秒，所以可以設定為 60 秒。若將它設置為 0，就禁止了 keepalive 連接。通常keepalive_timeout應該比client_body_timeout大
context: http, server, location
keepalive_timeout 60s;
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.
指定客戶端與服務端建立連接后發送 request body 的超時時間。如果客戶端在指定時間內沒有發送任何內容，Nginx 返回 HTTP 408（Request Timed Out）
context: http, server, location
client_body_timeout 20s;
客戶端向服務端發送一個完整的 request header 的超時時間。如果客戶端在指定時間內沒有發送一個完整的 request header，Nginx 返回 HTTP 408（Request Timed Out）。
# 配置段: http, server, location
client_header_timeout 10s
服務端向客戶端傳輸數據的超時時間。
context: http, server, location
send_timeout 30s;
客戶度連接nginx超時, 建議5s內
可以理解為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 within this time, the connection is closed.
