Skip to content

Inconsistent 429 coverage / Retry-After semantics across endpoints #126

Description

@Darkdruce

Summary

Only POST /payments can return 429 (with Retry-After: 1); other endpoints never rate-limit, and the fixed Retry-After: 1 ignores the actual quota window.

Location

  • src/api/mod.rs:180-190

Details & impact

Clients get inconsistent throttling behavior and a misleading retry hint.

Suggested fix

Uniform limiting (see related issue) and a Retry-After derived from the limiter state.

Acceptance criteria

  • 429 behavior and Retry-After are consistent and accurate.

Metadata

Metadata

Assignees

No one assigned

    Labels

    GrantFox OSSIssue tracked in GrantFox OSSMaybe RewardedIssue may be eligible for a GrantFox rewardOfficial Campaign | FWC26Campaign: Official Campaign | FWC26apiHTTP API surface and handlersreliabilityReliability, resilience, and fault-tolerance

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions