When Spring Cloud API Gateway Ratelimit is being used with Redis, X-RateLimit-Remaining being -1 in the response header indicates that an error occurred while retrieving the remaining rate limit from Redis. This could be due to Redis being unable to connect or an issue with the Redis configuration.
In this case, the API gateway may be unable to accurately track the rate limit for the user and may either restrict access prematurely or allow access beyond the rate limit. It is recommended to troubleshoot and resolve the issue with Redis to ensure proper rate limiting for the API.
Please start posting anonymously - your entry will be published after you log in or create a new account. This space is reserved only for answers. If you would like to engage in a discussion, please instead post a comment under the question or an answer that you would like to discuss
Asked: 2021-09-04 11:00:00 +0000
Seen: 10 times
Last updated: Aug 25 '21