I have two modules loaded and it looks like when I terminate a request from
one module by calling ngx_http_output_filter the body filter in the other
module does not get called. The module with the body filter is loaded first
in the config (IMO it shouldn't matter). Do you have any suggestion on how
I can make the body filter called?
I have a module which registers several events and I am using Nginx 1.12.1,
it looks like when I do a reload that the worker(s) hang and with the help
of strace I see that the events hanging are my events. I have added a
function on process exit but it does not get called (probably because of
the pending events). So my question is when should I delete the timers if
not on process exit?
I agree with Robert.
When adding those new directives, the "default" should match the old
behavior so people who are not aware of the new directives will NOT get any
unexpected results while upgrading to this release. People who has a need
to change the old behavior now will have the new directives in hand.
Can you make keepalive_timeout and keepalive_requests both default to
On Fri Aug 10 20:50:04 UTC 2018, Robert Paprocki wrote:
> Quite the patch. I recall this behavior being discussed a number of times
> in the past.
> Question: why the default of 100? This feels like a significantly breaking
> change wrt. the previous behavior. Are there any plans for advanced
> communication regarding this change, outside of a nominal changelog entry
> (e.g., "introduced 'keepalive_requests' directive")?