Skip to content

Retry-After, RateLimit.r parameter and example "Retry-After and slow down" #160

@ioggstream

Description

@ioggstream

Given

If a response contains both the Retry-After and the RateLimit header fields,
the Retry-After field value SHOULD NOT reference a point in time earlier than the reset parameter

I Expect

  • clarify the description (e.g., while in Example B.3 the Retry-After references a point in time earlier that the reset parameter, the quota is not yet fully consumed).

See also https://mailarchive.ietf.org/arch/msg/httpapi/prI-_67g4TdQJOnAP39lkU0mAyY/

TF: It would make sense to me if Retry-After has to be at least as late as
the RateLimit t= effective window when the available quota r= is zero,
but can be anything when the available quota r > 0.

Notes

HTTP/1.1 429 Too Many Requests
Content-Type: application/json
Retry-After: 20
RateLimit-Policy: "dynamic";q=100;w=60
RateLimit: "dynamic";r=15;t=40

{
  "status": 429,
  "detail": "Wait 20 seconds, then slow down!"
}

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions