Re: nginx-1.22.0 draft

On 24.05.2022 07:17, Maxim Dounin wrote: Hello! Below are patches for the nginx-1.22.0 release, and corresponding changes to the site. The nginx-1.22.0 release is based on nginx-1.21.6 with two additional changes grafted from the default branch: copyright year update and OpenSSL/zlib for win32

RE: SSL contexts reuse across locations

Hi, Attaching updated PoC patch, which also reuses contexts from 'http' level. > -Original Message- > From: Maxim Dounin > Sent: Friday, May 20, 2022 16:23 > > Hello! > > On Fri, May 20, 2022 at 06:52:54AM +, Pavel Pautov via nginx-devel wrote: > > > > -Original Message- >

Re: nginx-1.22.0 draft

Hello! On Tue, May 24, 2022 at 11:39:31AM +0400, Maxim Konovalov wrote: > On 24.05.2022 07:17, Maxim Dounin wrote: > > Hello! > > > > Below are patches for the nginx-1.22.0 release, and corresponding > > changes to the site. > > > > The nginx-1.22.0 release is based on nginx-1.21.6 with two > >

[nginx] Updated OpenSSL and zlib used for win32 builds.

details: https://hg.nginx.org/nginx/rev/8a54733c9d12 branches: changeset: 8011:8a54733c9d12 user: Maxim Dounin date: Tue May 24 02:51:49 2022 +0300 description: Updated OpenSSL and zlib used for win32 builds. diffstat: misc/GNUmakefile | 4 ++-- 1 files changed, 2 insertions(+),

[nginx] Stable branch.

details: https://hg.nginx.org/nginx/rev/c32b775633d3 branches: stable-1.22 changeset: 8012:c32b775633d3 user: Maxim Dounin date: Tue May 24 02:55:29 2022 +0300 description: Stable branch. diffstat: src/core/nginx.h | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diffs

[nginx] Year 2022.

details: https://hg.nginx.org/nginx/rev/dbf18f45a2b6 branches: stable-1.22 changeset: 8013:dbf18f45a2b6 user: Sergey Kandaurov date: Fri Feb 04 13:29:31 2022 +0300 description: Year 2022. diffstat: docs/text/LICENSE | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diffs (

[nginx] Updated OpenSSL and zlib used for win32 builds.

details: https://hg.nginx.org/nginx/rev/adbfc4fb948c branches: stable-1.22 changeset: 8014:adbfc4fb948c user: Maxim Dounin date: Tue May 24 02:51:49 2022 +0300 description: Updated OpenSSL and zlib used for win32 builds. diffstat: misc/GNUmakefile | 4 ++-- 1 files changed, 2 inse

[nginx] nginx-1.22.0-RELEASE

details: https://hg.nginx.org/nginx/rev/f669c9c2a617 branches: stable-1.22 changeset: 8015:f669c9c2a617 user: Maxim Dounin date: Tue May 24 02:59:18 2022 +0300 description: nginx-1.22.0-RELEASE diffstat: docs/xml/nginx/changes.xml | 14 ++ 1 files changed, 14 insertion

[nginx] release-1.22.0 tag

details: https://hg.nginx.org/nginx/rev/2d3ed138ce65 branches: stable-1.22 changeset: 8016:2d3ed138ce65 user: Maxim Dounin date: Tue May 24 02:59:19 2022 +0300 description: release-1.22.0 tag diffstat: .hgtags | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diffs (8 lines

Re: close request

Maxim, I am noticing this with our modules. Although, we do not do not message with any nginx reference counting etc. At most, we are sending 403-forbidden for some requests. Could you suggest some ways about debugging this? Thanks. Bhasker. ---

[njs] Version 0.7.4.

details: https://hg.nginx.org/njs/rev/b5198f7f11a3 branches: changeset: 1864:b5198f7f11a3 user: Dmitry Volyntsev date: Tue May 24 09:07:58 2022 -0700 description: Version 0.7.4. diffstat: CHANGES | 45 + 1 files changed, 45 insertions(+

[njs] Added tag 0.7.4 for changeset b5198f7f11a3

details: https://hg.nginx.org/njs/rev/640ed49b2dce branches: changeset: 1865:640ed49b2dce user: Dmitry Volyntsev date: Tue May 24 09:10:52 2022 -0700 description: Added tag 0.7.4 for changeset b5198f7f11a3 diffstat: .hgtags | 1 + 1 files changed, 1 insertions(+), 0 deletions(-)

[PATCH] Stream: don't flush empty buffers created for read errors.

In all honesty, the main motivation for the patch is to address a regression in UDP healthchecks caused by the behavior described below. It's already covered by tests, but the corresponding cases were disabled by default. I considered cl->buf->flush = !src->read->error; or even cl->buf->

Re: close request

Hello! On Tue, May 24, 2022 at 08:04:16AM -0700, Dk Jack wrote: > I am noticing this with our modules. Although, we do not do not message > with any nginx reference counting etc. > At most, we are sending 403-forbidden for some requests. Could you suggest > some ways about debugging this? Reques

[PATCH] Upstream: handling of certificates specified as an empty string

# HG changeset patch # User Sergey Kandaurov # Date 1653422583 -14400 # Wed May 25 00:03:03 2022 +0400 # Node ID 3bb1adbb74dfcd372f7369530967cfb415900778 # Parent 8a54733c9d1290e6dc2f86af18e8a976a6352e4f Upstream: handling of certificates specified as an empty string. Now, if the directive

RE: SSL contexts reuse across locations

Hi, Here is another iteration of patch, now it completely avoids creating SSL contexts without SSL proxying. Also changed some variable names and formatting in attempt to improve readability. Not sure about moving of merge/reuse logic into ngx_http_proxy_set_ssl(). I assume, it could look like