Requests to /a and /b converge on the same identity zone and client key. In the historical fixture, the first succeeds with 200 and the next is rejected with 429. Location names do not create separate budgets.

A request limit protects the budget named by its key

A request-rate limit applies to the identity expressed by its key, not automatically to a person, account, or endpoint. limit_req_zone stores shared state for those key values, and limit_req applies the zone while handling a request. Two locations using the same zone and key can consume the same budget. Choosing a variable therefore defines a real fairness and enforcement boundary. ...

August 28, 2027 · 6 min · XB Field Notes