<div style="line-height:1.7;color:#000000;font-size:14px;font-family:Arial">But if a connection to upstream is dead or there are some other network problems in this connection, how could Nginx handle it, will the HTTP requests on this connection be affected? For example, is it possible that the HTTP requests on this connection is hanging until timeout? <br><br><br><br><br><div style="position:relative;zoom:1"></div><div id="divNeteaseMailCard"></div><br><pre><br>At 2019-02-25 20:22:56, "Maxim Dounin" <email@example.com> wrote:
>On Mon, Feb 25, 2019 at 03:45:27PM +0800, yf chu wrote:
>> The Nginx document said that there are two upstream-related
>> directives introduced in the version of 1.15.3:
>> "keepalive_requests" and "keepalive_timeout". But the directive
>> "keepalive" has already been instroduced in the version of
>> 1.1.4. So I want to know how does Nginx handle the keepalive
>> connections for upstream before the version 1.15.3 was released.
>> When will the keepalive connections for upstream be closed?
>Before the introduction of "keepalive_requests" and
>"keepalive_timeout" directives in 1.15.3, upstream connections
>were simply kept open by nginx, regardless of the number of
>requests made in these connections, or the time these connections
>were idle. Connections were closed when the upstream server
>decided to close them, or when a connection was evicted from the
>cache by other connections.
>nginx mailing list
</pre></div><br><br><span title="neteasefooter"><p> </p></span>