When the rate-limiting plugin is in use for a service, we are seeing the following error. It also appears that Kong is returning a HTTP 500s because of this. We do see requests succeed (HTTP 200s) until the rate-limiting plugin throttles traffic and that's when we see HTTP 500s.
"2024/09/27 02:32:25 [error] 2567#0: *63070 [kong] init.lua:427 [rate-limiting] ./rate-limiting/handler.lua:212: arg #3 `value` for function `store_response_header` must be a string or a number, got nil, client: x.x.x.x, server: kong, request: \"POST /som/path HTTP/1.1\", host: \"some.host.com\", request_id: \"asdfasdfdsf\""
Expected Behavior
When using the rate-limiting plugin I expect no errors in the logs and when the rate-limiting plugin is in affect Kong should respond with HTTP 429 instead.
Is there an existing issue for this?
Kong version (
$ kong version
)Kong 3.8.0.0
Current Behavior
When the rate-limiting plugin is in use for a service, we are seeing the following error. It also appears that Kong is returning a HTTP 500s because of this. We do see requests succeed (HTTP 200s) until the rate-limiting plugin throttles traffic and that's when we see HTTP 500s.
Expected Behavior
When using the rate-limiting plugin I expect no errors in the logs and when the rate-limiting plugin is in affect Kong should respond with HTTP 429 instead.
Steps To Reproduce
Using this configuration
connect_timeout: 60000 read_timeout: 60000 write_timeout: 60000 retries: 5
name: my-app hosts:
Anything else?
We're running Kong on AWS ECS Fargate.