詳解Nginx的超時(shí)keeplive_timeout配置步驟
Nginx 處理的每個(gè)請(qǐng)求均有相應(yīng)的超時(shí)設(shè)置。如果做好這些超時(shí)時(shí)間的限定,判定超時(shí)后資源被釋放,用來(lái)處理其他的請(qǐng)求,以此提升 Nginx 的性能。
keepalive_timeout
HTTP 是一種無(wú)狀態(tài)協(xié)議,客戶(hù)端向服務(wù)器發(fā)送一個(gè) TCP 請(qǐng)求,服務(wù)端響應(yīng)完畢后斷開(kāi)連接。
如果客戶(hù)端向服務(wù)器發(fā)送多個(gè)請(qǐng)求,每個(gè)請(qǐng)求都要建立各自獨(dú)立的連接以傳輸數(shù)據(jù)。
HTTP 有一個(gè) KeepAlive 模式,它告訴 webserver 在處理完一個(gè)請(qǐng)求后保持這個(gè) TCP 連接的打開(kāi)狀態(tài)。若接收到來(lái)自客戶(hù)端的其它請(qǐng)求,服務(wù)端會(huì)利用這個(gè)未被關(guān)閉的連接,而不需要再建立一個(gè)連接。
KeepAlive 在一段時(shí)間內(nèi)保持打開(kāi)狀態(tài),它們會(huì)在這段時(shí)間內(nèi)占用資源。占用過(guò)多就會(huì)影響性能。
Nginx 使用 keepalive_timeout 來(lái)指定 KeepAlive 的超時(shí)時(shí)間(timeout)。指定每個(gè) TCP 連接最多可以保持多長(zhǎng)時(shí)間。Nginx 的默認(rèn)值是 75 秒,有些瀏覽器最多只保持 60 秒,所以可以設(shè)定為 60 秒。若將它設(shè)置為 0,就禁止了 keepalive 連接。
# 配置段: http, server, location keepalive_timeout 60s;
client_body_timeout
指定客戶(hù)端與服務(wù)端建立連接后發(fā)送 request body 的超時(shí)時(shí)間。如果客戶(hù)端在指定時(shí)間內(nèi)沒(méi)有發(fā)送任何內(nèi)容,Nginx 返回 HTTP 408(Request Timed Out)。
# 配置段: http, server, location client_body_timeout 20s;
client_header_timeout
客戶(hù)端向服務(wù)端發(fā)送一個(gè)完整的 request header 的超時(shí)時(shí)間。如果客戶(hù)端在指定時(shí)間內(nèi)沒(méi)有發(fā)送一個(gè)完整的 request header,Nginx 返回 HTTP 408(Request Timed Out)。
# 配置段: http, server, location client_header_timeout 10s;
send_timeout
服務(wù)端向客戶(hù)端傳輸數(shù)據(jù)的超時(shí)時(shí)間。
# 配置段: http, server, location send_timeout 30s;
客戶(hù)度連接nginx超時(shí), 建議5s內(nèi)
接收客戶(hù)端header超時(shí), 默認(rèn)60s, 如果60s內(nèi)沒(mé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.
接收客戶(hù)端body超時(shí), 默認(rèn)60s, 如果連續(xù)的60s內(nèi)沒(méi)有收到客戶(hù)端的1個(gè)字節(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時(shí)間,默認(rèn)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.
可以理解為T(mén)CP連接關(guān)閉時(shí)的SO_LINGER延時(shí)設(shè)置,默認(rèn)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.
域名解析超時(shí),默認(rèn)30s
Syntax: resolver_timeout time;
resolver_timeout 30s;
Sets a timeout for name resolution, for example:
resolver_timeout 5s;
發(fā)送數(shù)據(jù)至客戶(hù)端超時(shí), 默認(rèn)60s, 如果連續(xù)的60s內(nèi)客戶(hù)端沒(méi)有收到1個(gè)字節(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的連接超時(shí)時(shí)間
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ù)超時(shí), 默認(rèn)60s, 如果連續(xù)的60s內(nèi)沒(méi)有收到1個(gè)字節(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超時(shí), 默認(rèn)60s, 如果連續(xù)的60s內(nèi)沒(méi)有發(fā)送1個(gè)字節(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的超時(shí)keeplive_timeout配置步驟的文章就介紹到這了,更多相關(guān)Nginx 超時(shí)keeplive_timeout配置內(nèi)容請(qǐng)搜索腳本之家以前的文章或繼續(xù)瀏覽下面的相關(guān)文章希望大家以后多多支持腳本之家!
相關(guān)文章
詳解Nginx幾種常見(jiàn)實(shí)現(xiàn)301重定向方法上的區(qū)別
本篇文章主要介紹了詳解Nginx幾種常見(jiàn)實(shí)現(xiàn)301重定向方法上的區(qū)別,具有一定的參考價(jià)值,感興趣的小伙伴們可以參考一下2017-06-06詳解nginx前端根據(jù)$remote_addr分發(fā)方法
這篇文章主要介紹了詳解nginx前端根據(jù)$remote_addr分發(fā)方法,文中通過(guò)示例代碼介紹的非常詳細(xì),對(duì)大家的學(xué)習(xí)或者工作具有一定的參考學(xué)習(xí)價(jià)值,需要的朋友們下面隨著小編來(lái)一起學(xué)習(xí)學(xué)習(xí)吧2019-11-11使用Nginx搭建文件服務(wù)器及實(shí)現(xiàn)文件服務(wù)的步驟
Nginx是輕巧、高效的Web服務(wù)器,用作文件服務(wù)器非常合適,但是需要一些高級(jí)功能,如FTP遠(yuǎn)程訪問(wèn)、多用戶(hù)管理,可能需要選擇更為復(fù)雜的方案,例如Apache或FileZilla Server,這篇文章主要介紹了詳解如何使用Nginx搭建文件服務(wù)器及實(shí)現(xiàn)文件服務(wù),需要的朋友可以參考下2024-01-01nginx基于域名,端口,不同IP的虛擬主機(jī)設(shè)置的實(shí)現(xiàn)
這篇文章主要介紹了nginx基于域名,端口,不同IP的虛擬主機(jī)設(shè)置,文中通過(guò)示例代碼介紹的非常詳細(xì),對(duì)大家的學(xué)習(xí)或者工作具有一定的參考學(xué)習(xí)價(jià)值,需要的朋友們下面隨著小編來(lái)一起學(xué)習(xí)學(xué)習(xí)吧2020-11-11Nginx出現(xiàn)The plain HTTP request was sent to HTTPS port問(wèn)題解決方法
這篇文章主要介紹了Nginx出現(xiàn)The plain HTTP request was sent to HTTPS port問(wèn)題解決方法,需要的朋友可以參考下2015-04-04Nginx 啟動(dòng)、停止、重啟、升級(jí)操作命令收集
也許你不知道什么是Nginx,Nginx是一個(gè)WEB服務(wù)器,如IIS那樣,現(xiàn)在好多門(mén)戶(hù)都在使用了Nginx作為WEB服務(wù)器了,Nginx在Linux系統(tǒng)下跑很優(yōu)秀,強(qiáng)過(guò)其它的WEB服務(wù)端,還可以做負(fù)載均衡,很不錯(cuò)吧。2010-10-10nginx?rewrite?用法如何使用rewrite去除URL中的特定參數(shù)
日常服務(wù)中經(jīng)常會(huì)用Nginx做一層代理轉(zhuǎn)發(fā),把Nginx當(dāng)做前置機(jī),這篇文章主要介紹了nginx?rewrite?用法如何使用rewrite去除URL中的特定參數(shù),需要的朋友可以參考下2024-02-02