Nginx的超時timeout配置詳解
本文介紹 Nginx 的 超時(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 的默認(rèn)值是 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超時, 默認(rèn)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超時, 默認(rèn)60s, 如果連續(xù)的60s內(nèi)沒有收到客戶端的1個字節(jié), 返回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時間,默認(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.
可以理解為TCP連接關(guān)閉時的SO_LINGER延時設(shè)置,默認(rèn)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.
域名解析超時,默認(rèn)30s
Syntax: resolver_timeout time; Default: resolver_timeout 30s; Context: http, server, location Sets a timeout for name resolution, for example: resolver_timeout 5s;
發(fā)送數(shù)據(jù)至客戶端超時, 默認(rèn)60s, 如果連續(xù)的60s內(nèi)客戶端沒有收到1個字節(jié), 連接關(guān)閉
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數(shù)據(jù)超時, 默認(rèn)60s, 如果連續(xù)的60s內(nèi)沒有收到1個字節(jié), 連接關(guān)閉
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發(fā)送數(shù)據(jù)至upstream server超時, 默認(rèn)60s, 如果連續(xù)的60s內(nèi)沒有發(fā)送1個字節(jié), 連接關(guān)閉
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.
以上就是本文的全部內(nèi)容,希望對大家的學(xué)習(xí)有所幫助,也希望大家多多支持腳本之家。
相關(guān)文章
利用Nginx反向代理與負(fù)載均衡搭建多人測試環(huán)境詳解
這篇文章主要介紹了利用Nginx反向代理與負(fù)載均衡搭建多人測試環(huán)境的相關(guān)資料,文中介紹的非常詳細(xì),相信對大家具有一定的參考價值,需要的朋友們下面來一起看看吧。2017-04-04解決httpd占用80端口導(dǎo)致Nginx啟動失敗報錯的解決辦法
今天在建自己小網(wǎng)站時啟動Nginx時,發(fā)現(xiàn)其報下列錯誤,意思是因為80端口被占用導(dǎo)致Nginx啟動失敗,所以本文小編給大家介紹介紹如何解決解決httpd占用80端口導(dǎo)致Nginx啟動不成功報nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)2023-11-11解析阿里云centos7服務(wù)器nginx配置及常見問題解答
這篇文章主要介紹了阿里云centos7服務(wù)器nginx配置及常見問題解答,本文給大家介紹的非常詳細(xì),對大家的學(xué)習(xí)或工作具有一定的參考借鑒價值,需要的朋友可以參考下2020-07-07Nginx upstream的5種權(quán)重分配方式分享
Nginx upstream的5種權(quán)重分配方式分享,需要的朋友可以參考下2012-09-09