details: http://hg.nginx.org/nginx/rev/0237af43d409
branches:
changeset: 7212:0237af43d409
user: Ruslan Ermilov
date: Wed Feb 21 15:50:35 2018 +0300
description:
Version bump.
diffstat:
src/core/nginx.h | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diffs (14 lines):
details: http://hg.nginx.org/nginx/rev/88aad69eccef
branches:
changeset: 7214:88aad69eccef
user: Ruslan Ermilov
date: Wed Feb 21 15:50:43 2018 +0300
description:
Geo: optimized configuration parser.
If the geo block parser has failed, doing more things is pointless.
diffstat:
src
details: http://hg.nginx.org/nginx/rev/c69c13f10502
branches:
changeset: 7213:c69c13f10502
user: Ruslan Ermilov
date: Wed Feb 21 15:50:42 2018 +0300
description:
Geo: fixed memory allocation error handling (closes #1482).
If during configuration parsing of the geo directive the memo
details: http://hg.nginx.org/nginx/rev/2dc837d16099
branches:
changeset: 7215:2dc837d16099
user: Sergey Kandaurov
date: Wed Feb 21 17:26:00 2018 +0300
description:
Geo: fixed indentation.
diffstat:
src/stream/ngx_stream_geo_module.c | 22 +++---
1 files changed, 1
Hello!
On Tue, Feb 20, 2018 at 08:51:08PM +0100, Felix Ruess wrote:
> quite a while ago someone else already found the problem that the timeouts
> use system time rather than a monotonic clock:
> https://trac.nginx.org/nginx/ticket/189
>
> I updated/fixed the patch [1] there a while ago already
Greetings nginx developers,
The root cause analysis for a bug I observed during development of some
custom nginx module code turns out to be an unfortunate interaction between
sub-requests and indexed variable lookups using
ngx_http_get_indexed_variable(). We're based on nginx 1.13.6.
The sequenc