Skip to content
This repository has been archived by the owner on Nov 1, 2023. It is now read-only.

Custom Routes vs Query String #99

Open
mleonelli opened this issue Apr 21, 2017 · 0 comments
Open

Custom Routes vs Query String #99

mleonelli opened this issue Apr 21, 2017 · 0 comments

Comments

@mleonelli
Copy link

As you point out in the documentation

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant