Telize
Durch
Frederic Cambus |
Aktualisiert a month ago |
Location
Popularität
9.8 / 10
Latenz
84ms
Service Level
100%
Health Check
N/A
Zurück zu allen Diskussionen
Failing requests due to CORS Access control policy
clarifidev
5 years ago
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
Nehmen Sie an der Diskussion teil - fügen Sie unten einen Kommentar hinzu:
Anmelden / Registrieren, um neue Kommentare zu veröffentlichen
Hey I am still facing this issue on my localhost, Could you please let me know how to resolve this ?
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.
You’re welcome. Closing this as the issue is now resolved.
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
Hello,
Nothing changed regarding CORS on Telize side, we still send the following header:
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.