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

APIAP routing policy should only match paths that start with the routing path of the backend

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • None
    • 2.7 GA
    • System
    • None
    • 2
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • +
    • Hide
      • Add to a product a backend (e.g. Echo API) with routing path /v1
      • Define a product level mapping rule: /pets → hits
      • Promote the config
      • Perform a GET /v1/pets request and see the VALID response "No Mapping Rule matched"
      • Perform a GET /pets/v1 request and see an INVALID response 200
      Show
      Add to a product a backend (e.g. Echo API) with routing path /v1 Define a product level mapping rule: /pets → hits Promote the config Perform a GET /v1/pets request and see the VALID response "No Mapping Rule matched" Perform a GET /pets/v1 request and see an INVALID response 200
    • 3scale 2020-03-09, 3scale 2020-03-23

      APIAP routing policy currently matches all paths that contain the value chosen for the routing path of the backend and not only paths that start with such value. This is a bug and we need to fix it.

      Dev notes

      We need to wrap the regex built in https://github.com/3scale/porta/blob/9cba2310b44369bd6db468c71d89bd0756476910/app/models/config_path.rb#L12 within

      ^()

              Unassigned Unassigned
              mcassola Guilherme Cassolato
              Jakub Urban Jakub Urban (Inactive)
              Guilherme Cassolato Guilherme Cassolato
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: