[njs] Test262: fixed flaky fs tests.

details: https://hg.nginx.org/njs/rev/7d73d18e19f8 branches: changeset: 2347:7d73d18e19f8 user: Dmitry Volyntsev date: Wed May 29 22:23:55 2024 -0700 description: Test262: fixed flaky fs tests. Previously, two tests running in parallel could occasionally generate identical file name

[njs] Test262: fixed unstable fs test.

details: https://hg.nginx.org/njs/rev/7c671d50f646 branches: changeset: 2348:7c671d50f646 user: Dmitry Volyntsev date: Wed May 29 22:26:09 2024 -0700 description: Test262: fixed unstable fs test. Ensuring that symlink file is removed even if regular file does not exist. diffstat:

Re: [PATCH 2 of 2] Stream: do not reallocate a parsed SNI host

Hi, On Mon, May 27, 2024 at 02:21:44PM +0400, Sergey Kandaurov wrote: > # HG changeset patch > # User Sergey Kandaurov > # Date 1716805288 -14400 > # Mon May 27 14:21:28 2024 +0400 > # Node ID 88fa18a0f05f7dead38a127bb24e5cf861f3d66d > # Parent e82a7318ed48fdbc1273771bc96357e9dc232975 > Str

proxy_cache_lock for content revalidation

hello! it seems that the proxy_cache_lock directive operates only for cache misses (new content). while this behavior is documented, i am curious about the reasoning behind it. there are scenarios where proxy_cache_lock could be very beneficial for content revalidation. what are the community's th

[njs] Added contributing guide.

details: https://hg.nginx.org/njs/rev/509ae247a002 branches: changeset: 2349:509ae247a002 user: Dmitry Volyntsev date: Tue May 28 18:34:22 2024 -0700 description: Added contributing guide. diffstat: CONTRIBUTING.md | 95 + 1