Red Hat 3scale APIcast is redirecting the traffic to the wrong Product when using Path Based Routing

Solution Verified - Updated -

Issue

Using APIcast Path Based Routing, the mapping rule in the Product #1 we expect it to go to:

(GET) /path/to/resource/id

Instead it is going to this other Product #2, with this mapping:

(GET) /path/to/resource

Returning 403/HTTP. Is there a limit in how much of the path 3scale will look at for the mapping rule?

Environment

  • Red Hat 3scale API Management
    • SaaS
    • 2.X On-premises

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content