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
Claims that adding config line(s) to the bottom of the Schema file will modify the Response header accordingly.
Perhaps "star" would be a special case. Or perhaps not. The Docs do not specify if a "star" would cause the Response header to contain "star", OR if the header would echo back the Referrer header of the Request. Either way, it's not currently working.
For specifically listed domains one might assume the Response header would echo back the Request's "Referrer" header.
What version of Dgraph are you using?
Current DGraph Cloud version
Tell us a little more about your go-environment?
DGraph Cloud
Have you tried reproducing the issue with the latest release?
None
What is the hardware spec (RAM, CPU, OS)?
DGraph Cloud
What steps will reproduce the bug?
Try to apply a CORS setting. It won't work.
Expected behavior and actual result.
CORS settings get applied.
Additional information
Documentation here: https://dgraph.io/docs/graphql/security/cors/
Claims that adding config line(s) to the bottom of the Schema file will modify the Response header accordingly.
Perhaps "star" would be a special case. Or perhaps not. The Docs do not specify if a "star" would cause the Response header to contain "star", OR if the header would echo back the Referrer header of the Request. Either way, it's not currently working.
For specifically listed domains one might assume the Response header would echo back the Request's "Referrer" header.
Expected response header:
Actual response header: ❌
Expected response header from a request from https://localhost:3000
Actual response header: ❌
Expected response header from a request from https://example.com
Actual response header: ❌
Expected response header from a request from https://cloud.dgraph.io
Actual response header: ✅
The text was updated successfully, but these errors were encountered: