-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to set RequestRateLimiter as default filters via configuration properties #310
Comments
I also encountered this problem, how did you solve it later? |
@zhaoyibo 方便加你微信交流一下吗?我微信是Software_King |
@spencergibb Yes, I have read this configuration. But this configuration is for the specified route, this can work. However, what I said is that the default-filters are not for the specified route. |
It's the same, just under the default routes |
@spencergibb But it doesn't work, cannot find configuration for route. |
I see. |
@spencergibb have the problem been solved ? |
* Polish + Fixed service-registry endpoint + Added features endpoint docs Fixes spring-cloud#53 Fixes spring-cloud#310
in Finchley.RC1, I found that I can't configure defaultFilters with RequestRateLimiter like this
because AbstractRateLimiter#onApplicationEvent would not put the routeId and routeConfig to the config map.
if only add RequestRateLimiter to defaultFilters, only the defaultFilters contains the key
configurationPropertyName
, others don't have the key so they are not in config map.but RedisRateLimiter#isAllowed can't get the routeConfig through the specified routeId so we will get an exception.
exception
is it a bug or the designer deliberately did so?
The text was updated successfully, but these errors were encountered: