This morning, we started receiving the error below on all of our graphql API requests: Access to fetch at 'https://<registry name>.cdn.prismic.io/graphql?query=<query>' from origin 'http://localhost:3000' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the req…

We figured out the problem. At some point, support for querying by uid for _allDocuments was removed. We weren't passing in any uid, but removing the unused query parameter solved the problem. It would have been nice to have a more relevant error message, though.

Access to fetch at '....' has been blocked by CORS policy

Developing with Prismic

Phil (Phil Snow) closed , flag & select 'Something Else' to reopen. July 21, 2021, 3:12pm 18

Threads close after a period of inactivity. Flag this thread to re-open it and continue the conversation.

Topic		Replies	Views
Access has been blocked by CORS policy Developing with Prismic graphql	4	3342	December 9, 2021
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	2630	December 9, 2021
CORS Error using GraphQL endpoint Developing with Prismic	3	3135	March 31, 2023
GraphQL cors issue with fetch client side Developing with Prismic graphql	8	1154	December 9, 2021
Request header field prismic-ref is not allowed by Access-Control-Allow-Headers in preflight response Developing with Prismic graphql	43	7403	December 9, 2021

Access to fetch at '....' has been blocked by CORS policy

Related topics