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

Change error response when using path routing and the services doesn't have a matching path

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Done
    • Icon: Minor Minor
    • None
    • 2.2 GA, SaaS
    • Gateway

      When APICAST_PATH_ROUTING_ENABLED=true, APIcast first iterates over all services to find a service with:
      a) a matching public base URL
      b) a matching mapping rule

      However, if such a service is not found, APIcast falls back to the standard service matching algorithm which is – to pick the first service with matching public base URL.

      After the service is selected, APIcast first checks the authorization, and then the mapping rules. If the credentials are invalid for this service, the error that you get is "Authentication failed".

      The request is to change the logic of the path based routing logic, so it returns something like '404 Not Found' in case no service could be found for the Host + Path of the API request – instead of picking the service with the matching Host.

              Unassigned Unassigned
              rhn-support-avilatus Anna Vila Tusell
              David Ortiz David Ortiz (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: