Setting Access-Control-Allow-Origin headers for odata handler

[cpoliver]

Hey, I was hoping to be able to set the headers in the .meshrc.yaml to whitelist origins but I can't seem to figure out how to do so.

I've tried various combinations like this, but the headers don't seem to be coming back when I make requests to the mesh API.

    handler:
      odata:
        baseUrl: https://concept-api.iamcloud.net/api/
        expandNavProps: true
        operationHeaders:
          "Access-Control-Allow-Origin": http://localhost:3001
        schemaHeaders:
          "Access-Control-Allow-Origin": http://localhost:3001

Am I missing something obvious? Thanks in advance.

[ardatan]

Those headers are the ones sent with outgoing requests to OData API. You can implement your own GraphQL server that uses Mesh's schema with custom CORS configuration.

[cpoliver]

Hi @ardatan - thanks for clearing that up. Of course, that makes way more sense. Spent too much time in the client-side and was thinking there was some magical config I was missing rather than actually taking what mesh generates and using it to implement my own server.

[ardatan]

Now we can provide cors settings for serve command;
https://graphql-mesh.com/docs/recipes/as-gateway