How to correctly set up Product Mapping rules and Backend Public Paths with APIaaP

Solution Verified - Updated -

Issue

  • When a backend is configured to be accessible with a Public Path that is different from /, the gateway returns "404 - No Mapping Rule matched" and the connection is not successfully routed to that backend.

Environment

  • Red Hat 3scale API Management
    • SaaS
    • 2.7 On-Premises
    • 2.8 On-Premises
    • 2.9 On-Premises
    • 2.10 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