Thanks!
On Thu, Jan 12, 2023 at 1:36 PM J Carter wrote:
> It's trivial to do with error page OP as mentioned - an example:
>
> limit_req_status 598;
> limit_req_zone $binary_remote_addr zone=a:1m rate=1r/m;
>
> server {
> limit_req zone=a nodelay;
>
> error_page
It's trivial to do with error page OP as mentioned - an example:
limit_req_status 598;
limit_req_zone $binary_remote_addr zone=a:1m rate=1r/m;
server {
limit_req zone=a nodelay;
error_page 598 = @send-204;
location / {
...
}
.
Hello!
On Thu, Jan 12, 2023 at 05:16:21AM -0800, Christopher Liebman wrote:
> Not with 204.
> This works quite well with a partner that has an aversion to errors when
> they run over the limit:
> limit_req_status 204;
Indeed, 204 happens to be one of the two 2xx codes which can be
returned dire
Not with 204.
This works quite well with a partner that has an aversion to errors when
they run over the limit:
limit_req_status 204;
On Wed, Jan 11, 2023 at 12:22 PM Maxim Dounin wrote:
> Hello!
>
> On Mon, Jan 09, 2023 at 09:44:52AM -0800, Christopher Liebman wrote:
>
> > # HG changeset patch
Hello!
On Mon, Jan 09, 2023 at 09:44:52AM -0800, Christopher Liebman wrote:
> # HG changeset patch
> # User Christopher B. Liebman
> # Date 1672855906 28800
> # Wed Jan 04 10:11:46 2023 -0800
> # Node ID e438fab51202365305cace94aa25937081b051d0
> # Parent 07b0bee87f32be91a33210bc06973e07c4
# HG changeset patch
# User Christopher B. Liebman
# Date 1672855906 28800
# Wed Jan 04 10:11:46 2023 -0800
# Node ID e438fab51202365305cace94aa25937081b051d0
# Parent 07b0bee87f32be91a33210bc06973e07c4c1dac9
limit_req_status: allow status response to be as low as 200
No need to limit this
