You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, this is a very nice of software we'd like to use in our stack but it lacks of SkipList option which is very useful to allow certain clients to bypass limiter functionality. Would you be willing to consider to add this functionality? I need to stress out that in combination of custom HTTP header to use it will significantly increase its usage. For instance, the limiter can be applied to a custom HTTP header which identifies user, e.g. at CERN we use user's X509 DN. As such we can apply this to GRID jobs and limit users (abuser) based on their DN. But for production services we want to avoid that and can put their DNs in skip list if it will be provided.
The text was updated successfully, but these errors were encountered:
I provided a prototype of changes in this PR #186. I'm open to any implementations and only would like to stress out that such addition would be very useful for our use case.
vkuznet
changed the title
Please consider adding WhilteList option
Please consider adding SkipList option
Mar 28, 2022
Hi, this is a very nice of software we'd like to use in our stack but it lacks of SkipList option which is very useful to allow certain clients to bypass limiter functionality. Would you be willing to consider to add this functionality? I need to stress out that in combination of custom HTTP header to use it will significantly increase its usage. For instance, the limiter can be applied to a custom HTTP header which identifies user, e.g. at CERN we use user's X509 DN. As such we can apply this to GRID jobs and limit users (abuser) based on their DN. But for production services we want to avoid that and can put their DNs in skip list if it will be provided.
The text was updated successfully, but these errors were encountered: