Hello Srinivas,
I was facing the same issue and was able to work around the issue by allowing all origins in the CORS policy. Like so:
<cors>
<allowed-origins>
<origin>*</origin>
</allowed-origins>
<allowed-methods preflight-result-max-age="300">
<method>*</method>
</allowed-methods>
<allowed-headers>
<header>*</header>
</allowed-headers>
<expose-headers>
<header>*</header>
</expose-headers>
</cors>
The call works with this configuration, but is obviously not secure and cannot be used in production.
Were you able to find the correct URLs to be allowed for the connection to work?
Thanks,
Shridhar
WarrenBelz
146,745
Most Valuable Professional
RandyHayes
76,287
Super User 2024 Season 1
Pstork1
66,091
Most Valuable Professional