Description

MapStore currently handles HTTP 429 responses as a common error. The HTTP protocol defines clear semantics for rate limiting MapStore should respect them.

Acceptance criteria

When a resource returns 429, MapStore should:

• Respect the Retry-After header if present (both Retry-After: and Retry-After: forms per RFC 9110)
• Apply exponential backoff when Retry-After is absent, starting from a configurable base delay (e.g. 1s) with a configurable cap (e.g. 60s)
• Queue or defer pending requests to that same origin/resource during the backoff window, rather than dropping or firing them immediately