[nginx] Version bump.

details: http://hg.nginx.org/nginx/rev/2284008a2791 branches: changeset: 7085:2284008a2791 user: Sergey Kandaurov date: Wed Aug 09 14:59:44 2017 +0300 description: Version bump. diffstat: src/core/nginx.h | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diffs (14 lines

[nginx] Style.

details: http://hg.nginx.org/nginx/rev/577628e6b6a6 branches: changeset: 7086:577628e6b6a6 user: Sergey Kandaurov date: Wed Aug 09 14:59:46 2017 +0300 description: Style. diffstat: src/core/ngx_conf_file.c | 1 + src/event/ngx_event_openssl.c | 2 ++ src/h

[nginx] Fixed calls to ngx_open_file() in certain places.

details: http://hg.nginx.org/nginx/rev/47b7ffc3339d branches: changeset: 7087:47b7ffc3339d user: Sergey Kandaurov date: Wed Aug 09 15:03:27 2017 +0300 description: Fixed calls to ngx_open_file() in certain places. Pass NGX_FILE_OPEN to ngx_open_file() to fix "The parameter is incorr

set directive at http level

Hello, Do you think there is a problem in making the set directive available at http level (right now it's only server and lower). This would allow the usage of variables defined (and overridden in a lower config level) by set in directives like "map" and "log_format". Thanks. ___

Re: set directive at http level

On Wednesday 09 August 2017 23:17:13 Sorin Manole wrote: > Hello, > > Do you think there is a problem in making the set directive available > at http level (right now it's only server and lower). This would allow > the usage of variables defined (and overridden in a lower config > level) by set in