fix: add CORS headers to API Response#5906
Merged
Merged
Conversation
5 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
CORS was not setup for API routes. This meant that when working with Payload via an external server running on a different domain or port, it was not possible to use the REST or GraphQL APIs. Now, there's an OPTIONS endpoint to server a preflight response (just as before), and headers are set dynamically on the response based on the
corsproperty of the config (just as before). But unfortunately, we can't do this within Next.js middleware for this exact reason. Middleware currently supports only the Edge Runtime which currently cannot import the Payload config.