Upstream: fixed unexpected tcp_nopush usage on peer connections.
Now tcp_nopush on peer connections is disabled if it is disabled on
the client connection, similar to how we handle c->sendfile. Previously,
tcp_nopush was always used on upstream connections, regardless of
the "tcp_nopush" directive.
Maxim Dounin
4 years ago
1555 | 1555 | c->sendfile &= r->connection->sendfile; |
1556 | 1556 | u->output.sendfile = c->sendfile; |
1557 | 1557 | |
1558 | if (r->connection->tcp_nopush == NGX_TCP_NOPUSH_DISABLED) { | |
1559 | c->tcp_nopush = NGX_TCP_NOPUSH_DISABLED; | |
1560 | } | |
1561 | ||
1558 | 1562 | if (c->pool == NULL) { |
1559 | 1563 | |
1560 | 1564 | /* we need separate pool here to be able to cache SSL connections */ |