詳解Nginx的超時keeplive_timeout配置步驟
Nginx 處理的每個請求均有相應(yīng)的超時設(shè)置。如果做好這些超時時間的限定,判定超時后資源被釋放,用來處理其他的請求,以此提升 Nginx 的性能。
keepalive_timeout
HTTP 是一種無狀態(tài)協(xié)議,客戶端向服務(wù)器發(fā)送一個 TCP 請求,服務(wù)端響應(yīng)完畢后斷開連接。
如果客戶端向服務(wù)器發(fā)送多個請求,每個請求都要建立各自獨立的連接以傳輸數(shù)據(jù)。
HTTP 有一個 KeepAlive 模式,它告訴 webserver 在處理完一個請求后保持這個 TCP 連接的打開狀態(tài)。若接收到來自客戶端的其它請求,服務(wù)端會利用這個未被關(guān)閉的連接,而不需要再建立一個連接。
KeepAlive 在一段時間內(nèi)保持打開狀態(tài),它們會在這段時間內(nèi)占用資源。占用過多就會影響性能。
Nginx 使用 keepalive_timeout 來指定 KeepAlive 的超時時間(timeout)。指定每個 TCP 連接最多可以保持多長時間。Nginx 的默認值是 75 秒,有些瀏覽器最多只保持 60 秒,所以可以設(shè)定為 60 秒。若將它設(shè)置為 0,就禁止了 keepalive 連接。
# 配置段: http, server, location keepalive_timeout 60s;
client_body_timeout
指定客戶端與服務(wù)端建立連接后發(fā)送 request body 的超時時間。如果客戶端在指定時間內(nèi)沒有發(fā)送任何內(nèi)容,Nginx 返回 HTTP 408(Request Timed Out)。
# 配置段: http, server, location client_body_timeout 20s;
client_header_timeout
客戶端向服務(wù)端發(fā)送一個完整的 request header 的超時時間。如果客戶端在指定時間內(nèi)沒有發(fā)送一個完整的 request header,Nginx 返回 HTTP 408(Request Timed Out)。
# 配置段: http, server, location client_header_timeout 10s;
send_timeout
服務(wù)端向客戶端傳輸數(shù)據(jù)的超時時間。
# 配置段: http, server, location send_timeout 30s;
客戶度連接nginx超時, 建議5s內(nèi)
接收客戶端header超時, 默認60s, 如果60s內(nèi)沒有收到完整的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, 如果連續(xù)的60s內(nèi)沒有收到客戶端的1個字節(jié), 返回408
Syntax: client_body_timeout time;
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應(yīng)該比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連接關(guān)閉時的SO_LINGER延時設(shè)置,默認5s
Syntax: lingering_timeout time;
lingering_timeout 5s;
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;
resolver_timeout 30s;
Sets a timeout for name resolution, for example:
resolver_timeout 5s;
發(fā)送數(shù)據(jù)至客戶端超時, 默認60s, 如果連續(xù)的60s內(nèi)客戶端沒有收到1個字節(jié), 連接關(guān)閉
Syntax: send_timeout time;
send_timeout 60s;
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;
proxy_connect_timeout 60s;
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數(shù)據(jù)超時, 默認60s, 如果連續(xù)的60s內(nèi)沒有收到1個字節(jié), 連接關(guān)閉
Syntax: proxy_read_timeout time;
proxy_read_timeout 60s;
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發(fā)送數(shù)據(jù)至upstream server超時, 默認60s, 如果連續(xù)的60s內(nèi)沒有發(fā)送1個字節(jié), 連接關(guān)閉
Syntax: proxy_send_timeout time;
proxy_send_timeout 60s;
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.
到此這篇關(guān)于詳解Nginx的超時keeplive_timeout配置步驟的文章就介紹到這了,更多相關(guān)Nginx 超時keeplive_timeout配置內(nèi)容請搜索腳本之家以前的文章或繼續(xù)瀏覽下面的相關(guān)文章希望大家以后多多支持腳本之家!
相關(guān)文章
Nginx隱藏index.php和Pathinfo模式配置例子
這篇文章主要介紹了Nginx隱藏index.php和Pathinfo模式配置例子,需要的朋友可以參考下2014-04-04
Nginx訪問FTP服務(wù)器文件的時效性/安全校驗的方法
nginx的實現(xiàn)方式在校驗失敗的時候頁面返回error image,跳轉(zhuǎn)的是420 error_page,成功的時候會訪問FTP文件服務(wù)器的路徑,反正圖片到頁面展示,這篇文章主要介紹了Nginx訪問FTP服務(wù)器文件的時效性/安全校驗,需要的朋友可以參考下2023-12-12
Prometheus 和 Grafana 通過nginx-exporter監(jiān)控nginx的
nginx-exporter 是 Prometheus 用來從 Nginx 收集指標的組件,這篇文章給大家介紹Prometheus 和 Grafana 通過nginx-exporter監(jiān)控nginx的詳細步驟,感興趣的朋友跟隨小編一起看看吧2024-08-08

