Rate Limit by multiple types : Origin and HTTP_HEADER
angshuman-agarwal opened this issue · comments
Describe the question
I was rate liming by Origin (without any matchers) and now I want to Rate Limit by HTTP_HEADER too. I have added one line in the yaml file.
type:
- origin
- http_header=myCustomHeader
By doing this, will it rate limit "additionally" by header too i.e. request originating from an IP with that specific header will rate limited ? Note that origin does not have a matcher, but header is a specific one and has a matcher. Is this the correct way ?
If it is correct way, then, what is the best way to Test such that I can confirm that rate limiting is happening by both types ?
Thank you.
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 1 day