Package org.mockserver.mock.action.http

Class HttpQuotaRegistry

java.lang.Object

org.mockserver.mock.action.http.HttpQuotaRegistry

public class HttpQuotaRegistry
extends Object

Process-wide, stateful request quota for HTTP chaos — a fixed-window rate limiter, the HTTP counterpart of LlmQuotaRegistry. Unlike the probabilistic 429 in HttpChaosProfile (driven by errorProbability/errorStatus), this is deterministic and stateful: it counts how many requests have hit a named quota within the current time window and reports when the limit is exceeded, so a test can drive an application into a hard rate-limit (e.g. "the 4th call in 60s gets 429").

Quotas are keyed by name, so several expectations that share a quotaName share one counter (model an upstream account limit), while distinct names are independent. HTTP and LLM quotas are held in separate registries, so a HTTP and an LLM expectation that happen to use the same quotaName do not collide. State is held in a ConcurrentHashMap and each acquire is an atomic per-key update, safe under concurrent requests.

The time source is injectable so window behaviour is unit-testable without sleeping; production uses System.currentTimeMillis(). State is cleared on server reset (see HttpState.reset()).

Constructor Summary

Constructors

Constructor	Description
HttpQuotaRegistry(LongSupplier clock)

Method Summary

Modifier and Type	Method	Description
static HttpQuotaRegistry	getInstance()
void	reset()	Clear all quota state.
boolean	tryAcquire(String name, int limit, long windowMillis)	Record one request against the named quota and report whether it is allowed.

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Details

HttpQuotaRegistry

public HttpQuotaRegistry(LongSupplier clock)

Method Details

getInstance

public static HttpQuotaRegistry getInstance()

tryAcquire

public boolean tryAcquire(String name,
 int limit,
 long windowMillis)

Record one request against the named quota and report whether it is allowed.

Fixed-window semantics: the first request in a window starts it; the window expires windowMillis after it started, after which the next request starts a fresh window. A request is allowed when the in-window count (including itself) is at or below limit.

Returns:

true if the request is within the quota, false if it exceeds the limit for the current window.

reset

public void reset()

Clear all quota state. Called on server reset and for test isolation.