Hello, Maxim! It takes me some time to express new parameter with words, but finally it is as simple as "start to delay after N requests". I agree it more suitable then nodelay= and there is no need to warn about delay>burst. Thank you, I'll be very happy to see this feature in upstream. PS There
Hello!
On Sun, Oct 28, 2018 at 05:58:45PM +0300, Peter Shchuchkin wrote:
> # HG changeset patch
> # User Peter Shchuchkin
> # Date 1540737213 -10800
> # Sun Oct 28 17:33:33 2018 +0300
> # Node ID 70c0d476999d9b893c644606624134248ac7abad
> # Parent 874d47ac871a4b62fbe0ff5d469a8ad7bc5a4160
Hello!
Sorry, I've duplicated this message.
Additionally I've tried to send with hg email changes to nginx-test in the same
thread, but I'm not sure I've succeed and instead new thread was created with
changes in tests project.
Please review this changes, I hope this may be really useful for
# HG changeset patch
# User Peter Shchuchkin
# Date 1540737213 -10800
# Sun Oct 28 17:33:33 2018 +0300
# Node ID 70c0d476999d9b893c644606624134248ac7abad
# Parent 874d47ac871a4b62fbe0ff5d469a8ad7bc5a4160
Allow using nodelay=N semantics in limit_req configuration
This allows to use
# HG changeset patch
# User Peter Shchuchkin
# Date 1540737213 -10800
# Sun Oct 28 17:33:33 2018 +0300
# Node ID 70c0d476999d9b893c644606624134248ac7abad
# Parent 874d47ac871a4b62fbe0ff5d469a8ad7bc5a4160
Allow using nodelay=N semantics in limit_req configuration
This allows to use
