Add CORS headers to Ray App

[patinthehat]

I'm working on something that sends data to Ray from the browser, however due to a missing Access-Control-Allow-Origin header, I cannot send anything due to the CORS restrictions.

Can you add an option in preferences to modify this, or add Access-Control-Allow-Origin: * to the headers in the app's Express server?

Error message:

Access to XMLHttpRequest at 'http://127.0.0.1:23517/' from origin 'http://localhost:3344' 
has been blocked by CORS policy:

Response to preflight request doesn't pass access control check: 
No 'Access-Control-Allow-Origin' header is present on the requested resource.

[patinthehat]

The workaround I've come up with in the mean time is to run an http proxy that adds the required CORS headers.
You can check it out at permafrost-dev/ray-proxy.

[AdrianMrn]

What version of the app are you on? I added the required headers using the cors middleware in 1.2.5 or so.

[patinthehat]

Ray version: 1.3.0
OS: Ubuntu 20.04
Browser: Chromium 87

When I dump the headers from a POST request to Ray using curl, here's what I get:

HTTP/1.1 200 OK
X-Powered-By: Express
Content-Type: text/html; charset=utf-8
Content-Length: 2
ETag: W/"2-eoX0dku9ba8cNUXvu/DyeabcC+s"
Date: Thu, 14 Jan 2021 13:31:11 GMT
Connection: keep-alive

ok

and the headers from an OPTIONS request:

HTTP/1.1 200 OK
X-Powered-By: Express
Allow: POST
Content-Type: text/html; charset=utf-8
Content-Length: 4
ETag: W/"4-Yf+Bwwqjx254r+pisuO9HfpJ6FQ"
Date: Thu, 14 Jan 2021 13:34:09 GMT
Connection: keep-alive

POST

[AdrianMrn]

That's weird 😅

[patinthehat]

Strange.

Is it possible you're running a development version? (Or on a different OS?)
Could you list the express/cors package versions you're using?

[AdrianMrn]

[email protected]
[email protected]

I'm on Mac running a production version of Ray 1.3.0. I'm not sure what's going wrong 😬

I'm trying to find a solution.

[AdrianMrn]

Oh boy.

It'll be included in the next version 🙄

[patinthehat]

Fantastic. Thanks for looking into it!