Google URL Inspector Registers No 'Access-Control-Allow-Origin' Errors
(Doc ID 2972487.1)
Last updated on SEPTEMBER 11, 2023
Applies to:
Oracle Content Management - Version N/A and laterInformation in this document applies to any platform.
Goal
When I use the Google URL Inspection tool I can see the "Crawled Page" which fetches the page from the Google Search Index and a "Live Test" which is what has thrown CORS errors like:
Access to XMLHttpRequest at 'https://ocm.example.com/content/published/api/v1.1/items?' from origin 'https://www.example.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.
So it seems like Googlebot is behaving itself and crawling from the page with 'Origin' header so that 'Access-Control-Allow-Origin' is set, but the "Live Test" does not for some reason. Why is this behaviour occurring?
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Goal |
Solution |
References |