___
nginx-devel mailing list
[email protected]
http://mailman.nginx.org/mailman/listinfo/nginx-devel
On Tuesday 27 October 2015 20:52:43 Joel Cunningham wrote:
> Hi,
>
> I'm fairly new to the NGINX sources and have been studying ngx_array.c (from
1.9.5), particularly how the array grows when full.
>
> I'm having some confusion about how pool memory isn't leaked when the new
array size can not
___
nginx-devel mailing list
[email protected]
http://mailman.nginx.org/mailman/listinfo/nginx-devel
details: http://hg.nginx.org/nginx/rev/86b5f146b121
branches:
changeset: 6283:86b5f146b121
user: Valentin Bartenev
date: Tue Oct 27 23:16:29 2015 +0300
description:
Version bump.
diffstat:
src/core/nginx.h | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diffs (14 line
details: http://hg.nginx.org/nginx/rev/66ee1c5cb6aa
branches:
changeset: 6284:66ee1c5cb6aa
user: Valentin Bartenev
date: Tue Oct 27 23:16:35 2015 +0300
description:
HTTP/2: fixed spelling.
diffstat:
src/http/v2/ngx_http_v2.c | 4 ++--
1 files changed, 2 insertions(+), 2 deletions
Created a new patch as disabling hostame as a configuration option.
# HG changeset patch
# User Nils Hermansson <[email protected]>
# Date 1445973553 -3600
# Tue Oct 27 20:19:13 2015 +0100
# Node ID 7e4f788192183a3053cd9478ee136bad269a2375
# Parent f1424eef1966c966e5403c44e3d9470e0af5b7e9
Sys
Hello,
I could write a patch for that case. What would the recommended config
format be?
Example:
hostname=(on/off) default is on
access_log syslog:server=unix:/var/log/nginx.sock,hostname=off;
Regards
On Tue, Oct 27, 2015 at 3:14 PM, Vladimir Homutov wrote:
> On Fri, Oct 23, 2015 at 08:51
Hello Maxim,
Thanks for your input, it *is* appreciated.
As someone who has contributed to a large number of open source projects
throughout the years, it is however quite annoying to be pointed at the source
over and over again.
You seem to be thinking that I've never taken even a quick look
Hello!
On Tue, Oct 27, 2015 at 04:00:09PM +, Maxime Henrion wrote:
> Hey Sorin!
>
> First and foremost, thanks a lot for your answer.
>
> I started working on implementing a body filter for my needs,
> and am already facing some strange issues. When my body filter
> is called on the subre
I realized that the "pos" field is actually pointing right at the body of that
response, so that solves one of my issues.
I would however appreciate any documentation on those numerous flags sometimes
set in buffers and their actual meaning.
Maxime
From: nginx-d
Hey Sorin!
First and foremost, thanks a lot for your answer.
I started working on implementing a body filter for my needs, and am already
facing some strange issues. When my body filter is called on the subrequest I
sent, despite it being a body filter, I get a buffer chain containing the whole
On Fri, Oct 23, 2015 at 08:51:56PM +0200, Nils Hermansson wrote:
> # HG changeset patch
> # User Nils Hermansson <[email protected]>
> # Date 1445625283 -7200
> # Fri Oct 23 20:34:43 2015 +0200
> # Node ID 868fc6b3bf69be68c597578e749c65698b8c
> # Parent ee16fb0db905cfb858a929374cf623cdf1a0
details: http://hg.nginx.org/nginx/rev/f1424eef1966
branches:
changeset: 6282:f1424eef1966
user: Maxim Dounin
date: Tue Oct 27 16:47:30 2015 +0300
description:
release-1.9.6 tag
diffstat:
.hgtags | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diffs (8 lines):
diff --gi
details: http://hg.nginx.org/nginx/rev/b78018cfaa2f
branches:
changeset: 6281:b78018cfaa2f
user: Maxim Dounin
date: Tue Oct 27 16:47:29 2015 +0300
description:
nginx-1.9.6-RELEASE
diffstat:
docs/xml/nginx/changes.xml | 84 ++
1 files ch
14 matches
Mail list logo
