Question
![](/profiles/pega_profile/modules/pega_user_image/assets/user-icon.png)
Centene Corporation
US
Last activity: 17 Sep 2021 7:00 EDT
CORS request is blocked when a Pega Service HTTP is invoked from a third party application via browser
Issue:
We have a Service HTTP created in a Pega v7.2 application, this service is being invoked from an external application (AWS Connect Soft Phone Portal) via a browser like chrome. In the network trace it is seen that the request did not reach the server due to a CORS error.
Can someone please suggest on how to bypass the CORS configuration for Service HTTP rules in Pega v7.2?
Can we implement a CORS policy or restriction within Pega or at application server level?
Service HTTP format:
https://myapp.com/prweb/PRHTTPService/ServicePackage/Class/Method?Param1=123&Param2=123&Param3
Network Trace:
A cross-origin resource sharing (CORS) request was blocked because of invalid or missing response headers of the request or the associated preflight request . To fix this issue, ensure the response to the CORS request and/or the associated preflight request are not missing headers and use valid header values. Note that if an opaque response is sufficient, the request's mode can be set to no-cors to fetch the resource with CORS disabled; that way CORS headers are not required but the response content is inaccessible (opaque).