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

Calling a disabled method/endpoint returns 429

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 2.7 ER1
    • 2.5 GA
    • Gateway
    • None
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • +
    • Hide

      Deploy an API, Define mapping rules and methods. Disable the method in application plan. Call the endpoint.

      First time, it succeeds. After that, it returns 429.

      Show
      Deploy an API, Define mapping rules and methods. Disable the method in application plan. Call the endpoint. First time, it succeeds. After that, it returns 429.

      An endpoint/mapping rule is associated to a method. When that method on application plan is disabled as indicated in this screenshot, we were able to still call end point once and after that it returns Limits Exceeded message and returns 429 http status code. Since the method is disabled, should client/consumer not be able to call the endpoint even once and get 404 or 503 or something to the effect that endpoint is NOT available as part of the application plan?

              Unassigned Unassigned
              vkonda@redhat.com Vijay Konda (Inactive)
              Eloy Coto Eloy Coto
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: