amadan
The rastrillo side of this is rastrillo/rastrillo #36 (sign-in rate limits keyed on RemoteAddr).
Which client-address header can an app trust behind the edge? Question open
rastrillo's sign-in rate limit keys on RemoteAddr, and behind the edge every connection comes from the edge, so a whole tenant shares one budget (filed on rastrillo). To fix that, rastrillo needs to know which header the edge sets with the real client address, and that the edge always overwrites it (never passes through a client-supplied value) on every route kind: exec instance, unit, static.
Could the platform name that header in the contract, and say whether it holds on fleet boxes and through steering? Then rastrillo can trust it only when serving under CARLOS activation.
--- Filed from the ips repository (Turnkey's insolvency practice system, built on rastrillo v0.26.0 and deployed on CARLOS), where this was worked around. Paths without a repository prefix are in ips.