details: https://hg.nginx.org/njs/rev/077a5b2f30d8
branches:
changeset: 2336:077a5b2f30d8
user: Dmitry Volyntsev
date: Wed May 22 17:26:16 2024 -0700
description:
Improved String.prototype.replaceAll() for readability.
diffstat:
src/njs_string.c | 44
details: https://hg.nginx.org/njs/rev/e496851c0fe7
branches:
changeset: 2335:e496851c0fe7
user: Dmitry Volyntsev
date: Wed May 22 17:26:08 2024 -0700
description:
Fixed String.prototype.replaceAll() with zero length argument.
This fixes #712 issue on Github.
diffstat:
details: https://hg.nginx.org/njs/rev/bc09b884022d
branches:
changeset: 2334:bc09b884022d
user: Dmitry Volyntsev
date: Tue May 21 23:41:10 2024 -0700
description:
Aligned StringIndexOf() implementation with the spec.
When searchValue is empty the function should return early
when
details: https://hg.nginx.org/njs/rev/2d098d2a1c85
branches:
changeset: 2333:2d098d2a1c85
user: Dmitry Volyntsev
date: Tue May 21 23:41:10 2024 -0700
description:
Removed code for byte strings in built-in functions.
diffstat:
src/njs_array.c | 52
details: https://hg.nginx.org/njs/rev/27da19960b72
branches:
changeset: 2332:27da19960b72
user: Dmitry Volyntsev
date: Tue May 21 23:38:19 2024 -0700
description:
Avoid creating byte strings explicitly.
Previously, calls like njs_string_new(,,,0) produced byte strings by
explicitly
Hi,
Indeed there's a problem there. We have similar problems in other places as
well. Attached is a patch that fixes all I could find.
I did some testing for the sub_filter with the following config. Small buffers
exaggerate the problem.
http {
server {
listen 8000;