yalcinyildiz commented on issue #8218: URL: https://github.com/apache/apisix/issues/8218#issuecomment-1298367743
> > Until we reach the cache_ttl value; > > > > * When I invoke the service endpoint more than once, the "x-ratelimit-remaining" response header disappears > > * I can also hit the service endpoint more than the "x-ratelimit-limit" count. > > The priority of the `proxy-cache` plugin is higher than that of the `limit-count` plugin. When the cache hits, the `proxy-cache` will directly send the cached content to the client, and the `limit-count` plugin will not be executed. Ok, I see, but what if we want to limit user requests even when the cache mechanism is used? I believe such a scenario should be practical. > > 2.3.1 First call for the route > > apisix-cache-status response header is missing. > > From your configuration I see no problem, so please confirm the problem: > > 1. Is there any related error log? There is no log in error.log file. Here are the logs ithe n access.log file. 172.28.0.1 - - [01/Nov/2022:10:49:39 +0000] localhost:9079 "POST /hello.HelloGrpc/SayHello HTTP/2.0" 200 20 0.030 "-" "grpc-dotnet/2.42.0 (.NET 6.0.8; CLR 6.0.8; net6.0; windows; x64)" 192.168.1.78:9000 200 0.030 "grpc://192.168.1.78:9000" 172.28.0.1 - - [01/Nov/2022:10:49:43 +0000] localhost:9079 "POST /hello.HelloGrpc/SayHello HTTP/2.0" 200 20 0.000 "-" "grpc-dotnet/2.42.0 (.NET 6.0.8; CLR 6.0.8; net6.0; windows; x64)" - - - "http://localhost:9079"; > 2. Whether the request received the expected status code, etc. I expect to see a HttpStatus 429 when the user reaches the limit because to use cache or not is the choice of the apisix dashboard user. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
