#NO ACCESS CONTROL ALLOW ORIGIN HEADER CODE#

return [200, Discourse::Cors.apply_headers(cors_origins, env, We are trying to add the CORS header but still getting the error -> No Access-control-allow-origin Header is present on requested resource.cors_origins += rs_origins.split('|') if rs_origins.present?.CORS or Cross-Origin Resource Sharing is blocked in modern browsers by default (in JavaScript APIs). Simply activate the add-on and perform the request. Allow CORS: Access-Control-Allow-Origin lets you easily perform cross-domain Ajax requests in web applications. If you set this into the response header of the requested file, you will allow everyone to access the resources: > Not recommended allow all domains. Easily add (Access-Control-Allow-Origin: ) rule to the response header. To fix - in the API Gateway configuration - go to 'Gateway Responses', expand 'Default 4XX' and add a CORS configuration header there.

#NO ACCESS CONTROL ALLOW ORIGIN HEADER CODE#

discourse/discourse/blob/862773ec83756a2deb6beaabbcb16756a98595f9/config/initializers/008-rack-cors.rb#L13-L49 Header set Access-Control-Allow-Origin ' Solution 2: set headers the correct way. Also - if you happen to be getting a status code of 0 or 1 from a request running through API Gateway, this is probably your issue.

I think this is the part of code that handles the cors settings, just in case it is useful. Is there a way to confirm that the env vars are set correctly? (or that the app restart configured the cors without resending requests, just trying to think of ways to debug). The use of non-simple request headers here (Access-Control-Allow-Origin is not a simple header - and shouldn't be sent by the client - and application/json is a non-simple value for Content-Type) the browser is sending a preflight OPTIONS request, to check that the server permits these request headers via Access-Control-Allow-Headers.

No access control allow origin header