Layer7 API Management

  • 1.  Is there any workaround for CORS in v8.2 of the Gateway?

    Posted Aug 15, 2018 09:57 AM

    I have a service that is being developed in our gateway, and it has now come to my attention that the "Process CORS Request Assertion will need to be implemented in order for the service to work.

     

    However, the version of the Gateway we currently have is 8.2 and I do not believe this assertion exist for this version of the gateway. Though we are looking to update soon, I am not sure this will happen soon as we will have to coordinate a lot of user testing, for the many other services we hold on the gateway, and this portion can take weeks/months.

     

    And so my question is, is there anyway to implement something like the "Process CORS Request" in the 8.2 version of gateway?



  • 2.  Re: Is there any workaround for CORS in v8.2 of the Gateway?
    Best Answer

    Posted Aug 15, 2018 12:57 PM

    Hi David,

     

    We have a KB article on this here for your reference: https://comm.support.ca.com/kb/using-cors-preflight-caching-with-the-ca-api-gateway/kb000009657

     

    There is also already a community thread on this topic too, which I noticed has users own policy examples which differ from our own, so between ours and theirs, you should be covered here too: https://communities.ca.com/thread/241751617

     

    If the above links do not work for you, please let me know.

     

    On a side note, I wanted to provide you with a heads up that the 8.x series of API Gateway is coming to "End Of Service” on April 30, 2019. I strongly encourage you to upgrade to the 9.x series as soon as you are able to. The added benefit of that is you'll get the fully supported CORS assertion in the 9.1 or later versions of the CA API Gateway. ;-)