-
Notifications
You must be signed in to change notification settings - Fork 66
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
Append filter url to cache key #19
Comments
MarcGiffing
added a commit
that referenced
this issue
Dec 5, 2017
like that (123e092)? |
Haha. When will you release new version? |
MarcGiffing
added a commit
that referenced
this issue
Dec 6, 2017
Done!. It should be available in the maven central in the next hours. I would be nice if you can can test it. Thanks! |
Tested. It's pass my tests. Thanks for quick actions. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I suppose that the
expression
is evaluated into cache key, if so, only it is not enough to distinct the 2 rate limit configurations. How about adding filter url as prefix for cache key?Below are what I'm observing.
This doesn't work:
Append the request url make it work:
Here's how I test the above configuration.
userInfoes_post_tooMuch
will fail as it is executed aftersignUpCheck_post_tooMuch
, and thesignUpCheck...
set cache value to 20, which is exceed the limit foruserInfoes
.The text was updated successfully, but these errors were encountered: