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
{{ message }}
This repository has been archived by the owner on Nov 1, 2023. It is now read-only.
We were exploring this library, just getting our feet wet. We're trying to enable endpoint throttling on a URL match like
[Any HTTP Verb] at http://www.server.com/api/external/*
but the throttling limits themselves are set based on the ClientKey of each request (via override RequestIdentity SetIdentity() via a custom ThrottlingHandler)
Can we configure something like that today in your library? The main documentation makes it feel that setting the clientkey will apply that to all requests in the entire WebAPI pipeline.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
First off - great stuff and congrats!
We were exploring this library, just getting our feet wet. We're trying to enable endpoint throttling on a URL match like
[Any HTTP Verb]
athttp://www.server.com/api/external/*
but the throttling limits themselves are set based on the ClientKey of each request (via
override RequestIdentity SetIdentity()
via a customThrottlingHandler
)Can we configure something like that today in your library? The main documentation makes it feel that setting the clientkey will apply that to all requests in the entire WebAPI pipeline.
The text was updated successfully, but these errors were encountered: