Expand description
Limits on how much one client or one campaign can ask of a service, so a service open to the internet can’t be flooded or filled up: requests per minute from each client address (fewer for signing in), how big a request may be, and how much each campaign may keep.
All on by default. LIMITS=off turns every one off, for running on
your own machine, and LIMIT_<NAME>=<number> changes one, such as
LIMIT_CHARACTERS=1000 (the names are the fields below, in capitals).
Requests are counted per instance of a service, in memory, by client
address. Behind the HTTPS proxy every request comes from the proxy, so
TRUST_PROXY=1 takes the client’s address from the X-Forwarded-For
header the proxy adds instead, and counts only requests that came
through it: the services’ calls to each other (the combat service’s to
the character service, say) aren’t limited. Only set it where nothing
but the proxy and the other services can reach the service, or clients
could claim any address, or none.
Structs§
- Limits
- What a service allows; see the module’s description.