You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now on staging, we're getting this CORS error:
Solution
What I really want to do is go in to AWS API Gateway and adjust the CORS policy to allow for the Content-Type header, but everytime I do that I get a "network error" and it won't go through. I vaguely remember it being tricky to adjust the CORS policy previously, perhaps due to my lack of AWS permissions, although that's not indicated based on the error message, so I'm not really sure.
Technically, the Content-Type header is optional in this case, so it seems fine to just pull it out from the request itself? This did seem to resolve the problem for me.
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
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.
Problem
Right now on staging, we're getting this CORS error:

Solution
What I really want to do is go in to AWS API Gateway and adjust the CORS policy to allow for the Content-Type header, but everytime I do that I get a "network error" and it won't go through. I vaguely remember it being tricky to adjust the CORS policy previously, perhaps due to my lack of AWS permissions, although that's not indicated based on the error message, so I'm not really sure.
Technically, the Content-Type header is optional in this case, so it seems fine to just pull it out from the request itself? This did seem to resolve the problem for me.