Failing requests due to CORS Access control policy

Question

Started to get failure of requests from today ... see error below.... note I changed the requesting domain

Has something changed... shouldn't need to do pre-flight CORS requests for a GET

Access to XMLHttpRequest at 'https://telize-v1.p.mashape.com/geoip' from origin 'https://notmyrealdomain.com' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.

thx

David

Ashish1186 · Answer

Hey I am still facing this issue on my localhost,  Could you please let me know how to resolve this ?

smit zadfiya · Answer

Access to XMLHttpRequest at 'https://community-campbell.p.rapidapi.com/brandservice.svc/api/search?format=json&category=1&keyword=garlic&ingredient=beef' from origin 'http://localhost:8080' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.

Frederic Cambus · Answer

You're welcome. Closing this as the issue is now resolved.

clarifidev · Answer

Many thanks for response ... working today so as you say must have been a rapidapi issue.
We will also update the request to location
Cheers

DJ

Frederic Cambus · Answer

Hello,

Nothing changed regarding CORS on Telize side, we still send the following header:

```
Access-Control-Allow-Origin: *
```

However, RapidAPI are updating their infrastructure, so I would recommend contacting them at support@rapidapi.com and report the issue if you haven't done so already.

Also taking the opportunity to mention that the 'geoip' IP endpoint is deprecated, and the 'location' endpoint should be used instead. You should have received an email notification about this change. The announcements are available [here](https://market.mashape.com/fcambus/telize/announcements).

Best regards.

Telize

9.8 / 10

84ms

100%

N/A

Failing requests due to CORS Access control policy