Telize

PAID
By Frederic Cambus | Updated il y a 4 jours | Location
Popularity

9.8 / 10

Latency

85ms

Service Level

100%

Health Check

N/A

Back to All Discussions

Failing requests due to CORS Access control policy

Rapid account: Clarifidev
clarifidev
il y a 5 ans

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

Rapid account: Ashish 1186
Ashish1186 Commented il y a 3 ans

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

Rapid account: Srzsmitzadafiya 78
srzsmitzadafiya78 Commented il y a 4 ans

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.

Rapid account: Fcambus
fcambus Commented il y a 5 ans

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

Rapid account: Clarifidev
clarifidev Commented il y a 5 ans

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

Rapid account: Fcambus
fcambus Commented il y a 5 ans

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.

Best regards.

Join in the discussion - add comment below:

Login / Signup to post new comments