Process CORS request Assertion is working fine in Test & Dev environment (single node) but fails in UAT/prod environment.We have got 4 nodes in cluster in UAT/PROD env.
In Prod and UAT environment, CORS request is failing at "OPTION" call with "Abort" error.
When we stop the three nodes and keep only one active, it works. CORS request fails even with two nodes active in a cluster.
When you are using a cluster environment you should be using a VIP for the whole cluster so instead of node1.support.local, node2.support.local, etc it should be identified as something like ws.support.local and the certificate should reflect this name. In the origins setting in the Process CORS Request assertion you will need to identity the VIP name. For additional information I would recommend that you review this TechTip that one of our engineers produced
TechTip : When you need API Gateway Service to respond to both CORS and not CORS requests
Stephen HughesBroadcom Support