[nginx] Version bump.

details: https://hg.nginx.org/nginx/rev/2b2607d13fe9 branches: changeset: 7920:2b2607d13fe9 user: Roman Arutyunyan date: Fri Sep 03 17:19:33 2021 +0300 description: Version bump. diffstat: src/core/nginx.h | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diffs (14 line

[nginx] Fixed debug logging.

details: https://hg.nginx.org/nginx/rev/2245324a507a branches: changeset: 7921:2245324a507a user: Roman Arutyunyan date: Thu Sep 02 12:25:37 2021 +0300 description: Fixed debug logging. diffstat: src/http/v2/ngx_http_v2.c | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-)

[njs] Fixed AsyncFunction prototype property "name".

details: https://hg.nginx.org/njs/rev/91d9301684db branches: changeset: 1705:91d9301684db user: Dmitry Volyntsev date: Fri Sep 03 14:57:50 2021 + description: Fixed AsyncFunction prototype property "name". According to the spec the AsyncFunction prototype does not have own prope

Re: About the phase handlers init

Hello! On Fri, Sep 03, 2021 at 12:08:32PM +0800, Jinhua Luo wrote: > In the function ngx_http_init_phase_handlers, I found two places hard > to understand. > > a) The n variable is as known as the next phase handler index. In the > switch case NGX_HTTP_ACCESS_PHASE, it invokes n++, which seems t