Uploaded image for project: 'Red Hat 3scale API Management'
  1. Red Hat 3scale API Management
  2. THREESCALE-1380

Return a 'retry-after' header when the request is rate limited

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Done
    • Major
    • None
    • 2.3 CR1
    • Gateway
    • None

    Description

      Return a 'retry-after' header when the request is rate limited.

      See https://github.com/3scale/apicast/issues/335#issuecomment-427361128 for context.

      Requires fix in apisionator, see https://github.com/3scale/apisonator/issues/54

      This is proposed to be included as Technical Preview in 2.4. It will have to be included in the release notes. No visual element to flag as such. I suggest to create a KCS article for this.

      Attachments

        Issue Links

          is documented by

          Task - Represents a small unit of work that is not end-user facing. THREESCALE-1513 Document: Return a 'retry-after' header when the request is rate limited

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is related to

          Feature Request - Feature requests from customers and/or users THREESCALE-121 Provide rate limit quotas in response headers

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Activity

            People

              dortiz-1 David Ortiz (Inactive)
              vramosp Vanessa Ramos (Inactive)
              Peter Stanko Peter Stanko (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: