Is a dynamic rate limit based on request headers possible?

[Olu]

Do you mean quota instead of rate-limit?

I replied to a similar question previously. I have grabbed my response and shared it here

Quota and Failure 40x, avoid decrement

Hello @Michal_Gorski and welcome to the community I don’t think this is possible via Tyk out of the box. Rate limit and quota updates occur on the request after authentication, but before it is proxied upstream. As such the quota is considered/deducted before a response is received. You could achieve your goal with the help of custom plugins especially with golang or python. The crux involves making a seperate connection to redis and then modifying the key with quota- prefix. Y…

@rbrady98

Overall, is a Go plugin running post_auth able to dynamically change the rate limit based on a request header.

It might be as long as you can retrieve and modify the rate limit key in Redis rate-limit-<UNHASHED_ID_OR_HASH>

An alternative approach may be to disable quota and rate-limiting but use the key’s metadata field to manually manage your dynamic rate limit or quota. It would involve a lot of effort in you implementing everything. Please note this suggestion is only a theory and hasn’t been tested.