Hi! Would it be possible to add Access-Control-Allow-Origin: * header to javascript assets that are used by browser. It will help us to see errors in these third-party scripts. Currently we can see only Script error in our logs and Datadog advises to do these steps to reveal the errors. For example…

Hey @tech.microsites.plat , have you checked out this similar post? [image] Request header field prismic-ref is not allowed by Access-Control-Allow-Headers in preflight response Developing with Prismic Hi guys, I have a CORS problem, can you help me? The question is: Acce…

Hey Pau, in this case it's more about assets like prismic.min.js and toolbar.js files. In the post you sent I see discussions about graphQL requests. My guess is that this case will be easy since it's a matter of adding one header to these static assets.

Access-Control-Allow-Origin: * in assets

Developing with Prismic

Pau July 31, 2023, 2:38pm 2

Hey @tech.microsites.plat, have you checked out this similar post?

Topic		Replies	Views
Access to fetch at <Fetching API URL> from origin 'http://localhost:3000' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource Developing with Prismic graphql	3	2675	December 9, 2021
Access has been blocked by CORS policy Developing with Prismic graphql	4	3391	December 9, 2021
CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource Developing with Prismic rest-api	3	1156	December 9, 2021
Static.cdn.prismic.io Cross Origin Resource Policy Developing with Prismic javascript	1	231	September 15, 2023
GraphQL CORS Missing Allow Origin Header Developing with Prismic graphql	10	1800	December 9, 2021

Access-Control-Allow-Origin: * in assets

Related topics