CORS Configuration returning null #6224
Unanswered
curtis-thompson
asked this question in
Q&A
Replies: 1 comment 2 replies
-
That's for the security. The server protects the information of the allowed origins so it cannot try to bypass preflight check. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello, I'm configuring the CORS settings on our GraphQL Mesh instance using these docs. I have a list of allowed origins which I am setting in the mesh yaml like the following:
When I send a request to my GraphQL Mesh instance from the allowed origins (
https://allowed-origin-1.com
orhttps://allowed-origin-2.com
) I get the expected response, with theAccess-Control-Allowed-Origin
response header set to the host.However, when I send a request to my GraphQL Mesh instance from a different (not allowed) origin, say
https://not-allowed-origin
theAccess-Control-Allow-Origin
header gets set tonull
. Is there something wrong with my configuration?Many thanks in advance
Beta Was this translation helpful? Give feedback.
All reactions