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.
If, from the same IP, in the same second, you'll make two calls to api/values, the last call will get blocked. But if in the same second you call api/values/1 too, the request will go through because it's a different route.
Is there any development / workaround to consider
/api/values
and /api/values/{0}
the same in terms of throttling?
Considering the element as, let's say value_id, if you serve
/api/values?value_id={0}
The latter is counted in the same throttling as the collection call.
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.
As you point out in the documentation
Is there any development / workaround to consider
/api/values
and
/api/values/{0}
the same in terms of throttling?
Considering the element as, let's say value_id, if you serve
/api/values?value_id={0}
The latter is counted in the same throttling as the collection call.
The text was updated successfully, but these errors were encountered: