[PATCH 0 of 1] Upstream: add propagate_connection_close directive

Maxim Dounin mdounin at mdounin.ru
Tue Jan 13 15:18:36 UTC 2015


On Wed, Jan 07, 2015 at 07:06:38PM -0800, Shawn J. Goff wrote:

> On 01/04/2015 07:47 PM, Maxim Dounin wrote:
> >If there is a need to allow dynamic control of keepalive, I think
> >that proper way would be to extend the "keepalive_disable"
> >directive with variables support.
> >
> Thanks for this suggestion. I started exploring this option today. The
> keepalive directive is used to set the keepalive field on the request struct
> in the find_config_phase before we have the content. The Connection header
> is later added in a filter. If I need to make keepalive_disable have
> variable support that can use the $http_ variables (or something else that
> depends on the content), I need to do this after we have the content and
> before the filter.
> Should I continue down this path, or am I misunderstanding what you mean
> here?

Yes, this approach will require testing of variables specified in 
the keepalive_disable at some point later, probably in the header 
filter of the header filter chain.

Maxim Dounin

More information about the nginx-devel mailing list