The Cross-Origin Resource Sharing (CORS) Policy returns HTTP 403 (Forbidden) when 'APICAST_PATH_ROUTING=true' on Red Hat 3scale API Management

Solution Verified - Updated -

Issue

  • If the Cross-Origin Resource Sharing (CORS)CORS Policy is not enabled for all the Services, the preflight HTTP OPTIONS request will fail and return a 403 (Forbidden) response.
  • When we define a CORS policy for an API using APICAST_PATH_ROUTING=true, it is not effective unless we have the same CORS policy on all the Red Hat 3scale APIs.

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