Hello!
A user of mine, rvsw, reported an issue in the $args builtin variable.
Setting $args does not change the r->valid_unparsed_uri flag so
modules like ngx_proxy might still use the unparsed URI even when the
$args has been assigned to a new value.
A minimal example that can reproduce this is
Hi all,
We have a media server and we protect certain files from being accessed by
external ips, we just allow access from our static ip. Everything works ok
and a 403 is thrown to those who try to access the files.
server {
listen ***;
root ***;
{some other settings}
# protec
details: http://hg.nginx.org/nginx/rev/a387ce36744a
branches:
changeset: 5538:a387ce36744a
user: Tatsuhiko Kubo
date: Thu Jan 23 22:09:59 2014 +0900
description:
Typo fixed.
diffstat:
src/http/modules/ngx_http_range_filter_module.c | 2 +-
1 files changed, 1 insertions(+), 1 dele
On Thursday 23 January 2014 22:30:40 cubicdaiya wrote:
> # HG changeset patch
> # User Tatsuhiko Kubo
> # Date 1390482599 -32400
> # Thu Jan 23 22:09:59 2014 +0900
> # Node ID 5fe4d5140563b51a6530847e7e3a5d2a2031bd8a
> # Parent fff0f73673c3dbe09348913b61925994881bf72e
> fix typo
>
[..]
Tha
details: http://hg.nginx.org/nginx/rev/2a81949cbd7c
branches:
changeset: 5536:2a81949cbd7c
user: Maxim Dounin
date: Thu Jan 23 18:32:25 2014 +0400
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/49b1ad48b55c
branches:
changeset: 5537:49b1ad48b55c
user: Maxim Dounin
date: Thu Jan 23 18:32:26 2014 +0400
description:
SSL: fixed $ssl_session_id possible segfault after 97e3769637a7.
Even during execution of a request it is possible that the
# HG changeset patch
# User Tatsuhiko Kubo
# Date 1390482599 -32400
# Thu Jan 23 22:09:59 2014 +0900
# Node ID 5fe4d5140563b51a6530847e7e3a5d2a2031bd8a
# Parent fff0f73673c3dbe09348913b61925994881bf72e
fix typo
diff -r fff0f73673c3 -r 5fe4d5140563
src/http/modules/ngx_http_range_filter_modu
