Fedora Account System
Red Hat Associate
Red Hat Customer
When a TokenRateLimitPolicy is applied alongside an AuthPolicy on the same HTTPRoute, unauthenticated requests unexpectedly return HTTP 200 instead of 401 and reach the backend. The same failure occurs when a RateLimitPolicy with defaults or overrides is attached to the Gateway or listener of a route carrying a TokenRateLimitPolicy. Configured rate limits (5/min and 10/min) are not enforced, even with a burst of 30 requests. Removing the TokenRateLimitPolicy restores the expected authentication behavior, while a regular request-based RateLimitPolicy correctly enforces both authentication (401) and rate limiting (429). Gateway logs show Limitador response JSON parsing and CEL predicate evaluation errors. The suspected root cause is that a response-body store action prepended to the WASM action chain cannot settle during the request phase, leaving the authentication guard pending and preventing the auth check from being dispatched.