• 超时时间proxy_read_timeout和fastcgi_read_timeout 详解


    使用nginx服务器如果遇到timeou情况时可以如下设置参数,使用fastcgi:

    fastcgi_connect_timeout 75; 链接

    fastcgi_read_timeout 600; 读取

    fastcgi_send_timeout 600; 发请求

    这两个选项.
    fastcgi_read_timeout是指fastcgi进程向nginx进程发送response的整个过程的超时时间
    fastcgi_send_timeout是指nginx进程向fastcgi进程发送request的整个过程的超时时间

    这两个选项默认都是秒(s),可以手动指定为分钟(m),小时(h)等

    keepalive_timeout

    HTTP 是一种无状态协议,客户端向服务器发送一个 TCP 请求,服务端响应完毕后断开连接。

    如果客户端向服务器发送多个请求,每个请求都要建立各自独立的连接以传输数据。

    HTTP 有一个 KeepAlive 模式,它告诉 webserver 在处理完一个请求后保持这个 TCP 连接的打开状态。若接收到来自客户端的其它请求,服务端会利用这个未被关闭的连接,而不需要再建立一个连接。

    KeepAlive 在一段时间内保持打开状态,它们会在这段时间内占用资源。占用过多就会影响性能。

    Nginx 使用 keepalive_timeout 来指定 KeepAlive 的超时时间(timeout)。指定每个 TCP 连接最多可以保持多长时间。Nginx 的默认值是 75 秒,有些浏览器最多只保持 60 秒,所以可以设定为 60 秒。若将它设置为 0,就禁止了 keepalive 连接。通常 keepalive_timeout 应该比 client_body_timeout(见下文)大.

    # 配置段: http, server, location

    keepalive_timeout 60s;

    client_body_timeout

    指定客户端与服务端建立连接后发送 request body 的超时时间。如果客户端在指定时间内没有发送任何内容,Nginx 返回 HTTP 408(Request Timed Out)。

    # 配置段: http, server, location

    client_body_timeout 20s;

    client_header_timeout

    客户端向服务端发送一个完整的 request header 的超时时间。如果客户端在指定时间内没有发送一个完整的 request header,Nginx 返回 HTTP 408(Request Timed Out)。

    # 配置段: http, server, location

    client_header_timeout 10s;

    send_timeout

    服务端向客户端传输数据的超时时间,根据转发的应用服务可以配置 proxy_send_timeout、uwsgi_send_timeout、fastcgi_send_timeout(见下文)。

    # 配置段:http, server, location

    send_timeout 30s;
    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.

    client_header_timeout

    接收客户端 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.

    client_body_timeout

    接收客户端 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.

    lingering_timeout

    可以理解为 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.

    resolver_timeout

    域名解析超时,默认 30s

    Syntax: resolver_timeout time;

    Default:

    resolver_timeout 30s;

    Context: http, server, location

    Sets a timeout for name resolution, for example:

    resolver_timeout 5s;

    proxy_connect_timeout

    nginx 与 upstream server 的连接超时时间,默认为 60s;根据应用不同可配置 uwsgi_send_timeout/fascgi_send_timeout/proxy_send_timeout

    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.

    proxy_read_timeout

    nginx 接收 upstream server 数据超时, 默认 60s, 如果连续的 60s 内没有收到 1 个字节, 连接关闭;根据应用不同可配置 uwsgi_send_timeout/fascgi_send_timeout/proxy_send_timeout

    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.

    proxy_send_timeout

    nginx 发送数据至 upstream server 超时, 默认 60s, 如果连续的 60s 内没有发送 1 个字节, 连接关闭;根据应用不同可配置 uwsgi_send_timeout/fascgi_send_timeout/proxy_send_timeout。

    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 rec


    参考:https://ld246.com/article/1543809580828

    https://blog.csdn.net/mnasd/article/details/80253628

  • 相关阅读:
    所谓的底层问题
    字符流与字节流
    字节和字符,对信息进行编码
    Asp.net和数据库的一些概念
    谈.NET,由编译器开始谈起
    Extjs中的dom,Ext.Element和Ext.Component对象的关系
    WCF和Delphi通信时序列化的问题
    认真的考虑了下领域模型,发现设计是最难的部分。书上的例子各个对象职责划分的不错,可惜能看懂不代表能设计出。
    MS100 [011020]
    MS100[001]
  • 原文地址:https://www.cnblogs.com/kumufengchun/p/15719935.html
Copyright © 2020-2023  润新知