Re: Open-sourcing periodic upstream server resolution and implementing a dedicated service worker.

Hi Vladimir I hope you don't mind me chipping in here. We currently have 2 services which use Nginx with upstreams whose DNS can change frequently (e.g. AWS S3, ELB/ALB origins) so we're familiar with this problem. Initially we did a config reload every minute to solve the issue but since then,

Re: [PATCH] SSL: consistent certificate verification depth

> On 20 Jul 2022, at 22:04, Maxim Dounin wrote: > > Hello! > > On Wed, Jul 20, 2022 at 05:58:26PM +0400, Sergey Kandaurov wrote: > >> # HG changeset patch >> # User Sergey Kandaurov >> # Date 1658325446 -14400 >> # Wed Jul 20 17:57:26 2022 +0400 >> # Node ID 5a9cc2a846c9ea4c0af03109ab186af1a

Re: Open-sourcing periodic upstream server resolution and implementing a dedicated service worker.

Hi Neil Thank you for sharing your perspectives. TTL-based DNS re-resolving is planned for this feature. Also, nginx resolver (which we plan to use) supports "ipv6=off" and (since 1.23.1) "ipv4=off" parameters for cases when IPv6 or IPv4 addresses are not desired. We know about solutions bas

[njs] Fixed assignment to global property by name only.

details: https://hg.nginx.org/njs/rev/4b8d8237f598 branches: changeset: 1916:4b8d8237f598 user: Vadim Zhestikov date: Thu Jul 21 18:33:20 2022 -0700 description: Fixed assignment to global property by name only. This closes #145 issue on Github. diffstat: src/njs_generator.c