details: http://hg.nginx.org/nginx/rev/58956c644ad0
branches:
changeset: 5924:58956c644ad0
user: Maxim Dounin
date: Fri Nov 28 16:57:23 2014 +0300
description:
Typo.
diffstat:
src/core/ngx_crypt.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diffs (12 lines):
diff -
details: http://hg.nginx.org/nginx/rev/c76d851c5e7a
branches:
changeset: 5925:c76d851c5e7a
user: Maxim Dounin
date: Fri Nov 28 16:57:50 2014 +0300
description:
Fixed post_action to not trigger "header already sent" alert.
The alert was introduced in 03ff14058272 (1.5.4), and was tri
details: http://hg.nginx.org/nginx/rev/08bfc7188a41
branches:
changeset: 5926:08bfc7188a41
user: Maxim Dounin
date: Fri Nov 28 16:58:39 2014 +0300
description:
Write filter: fixed handling of sync bufs (ticket #132).
diffstat:
src/http/ngx_http_write_filter_module.c | 13
Sorry if this is not the place to ask this or if this has been asked before
(google hasn't been helpful), but I'm unsure of how to proceed with this
problem.
I am developing a body filter module that processes html and has to do a
process in the middle of sending a response that can take upward
Hi Maxim!
On Thu, Nov 27, 2014 at 7:31 AM, Maxim Dounin wrote:
> Yichun, I've spent some time looking in this, and I don't see how
> it can cause infinite hang at least with stock nginx modules. It
> certainly can cause suboptimal behaviour though, both with proxy
> cache locks and with AIO.
>
Y
Hello!
On Fri, Nov 28, 2014 at 2:46 PM, Tod Baudais wrote:
> I am developing a body filter module that processes html and has to do a
> process in the middle of sending a response that can take upwards of a
> couple seconds.
What is this "process" exactly? Is it CPU-bound computation or just a
(n
