AWS Lambda - No 'Access-Control-Allow-Origin' header is present on the requested resource

Question

I have AWS lambda function that I am trying to call from my web app using Axios. It keeps giving the error: 'http://localhost:3000' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.

I am using serverless and I have added the cors:true attribute to my function. I have also added:

 const response = { statusCode:200, headers: { 'Access-Control-Allow-Origin': '*', 'Access-Control-Allow-Credentials': true }, body: JSON.stringify({ message: 'Ticket received', TableData: data, }), }; callback(null, response);

I still can't get this issue resolve. Any help is greatly appreciated.

Possible duplicate of API Gateway CORS: no 'Access-Control-Allow-Origin' header — Ravi Ram
– Ravi Ram, Commented Jun 11, 2019 at 20:54

Daniel Edwards · Accepted Answer · 2019-01-16 09:48:23Z

1

I was returning 2 different responses, the one above and an error response. Once I defined the error message to have the headers it then worked fine.

answered Jan 16, 2019 at 9:48

Daniel Edwards

1013 silver badges10 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Ravi Ram Over a year ago

Please show an example code snippet to help the next person

Daniel Edwards Over a year ago

const response = { statusCode:500, headers: { "Access-Control-Allow-Origin" : "*", // Required for CORS support to work "Access-Control-Allow-Credentials" : true }, body: JSON.stringify({ message: 'Failed to add ticket to the database.', error: err }), }; callback(null, response);

Collectives™ on Stack Overflow

AWS Lambda - No 'Access-Control-Allow-Origin' header is present on the requested resource

1 Answer 1

2 Comments

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

2 Comments

Linked

Related