Janko Marohnić @janko.io · Jul 17 That's my 2nd blocker for replacing rack-attack. The 1st one is the inability to access rate limiting state for response headers to communicate rate limits to the caller. This is what we have at the moment:
0 likes 1 replies
?
Replies
Curious why you don't prefer to specify rate limits per controller, seems clearer in our case. As far as state, it seems to be kept in redis, have you tried digging in to see what/how it stores? (I haven't)