Postman [POST] request body is not parsing correctly

Question

So I'm trying to enable the post method to my AWS Lambda function that is connected to the AWS API Gateway. The lambda function is created from one of the examples from serverless-chrome. (The pdf function)

I'm trying to print the event variable to get the body sent via POST request using Postman. My Post Body http://joxi.ru/Drl1qPKfvg6Bjm but when I watch the logs in CloudWatch, I get an output like this:

"body":"dXJsPWh0dHAlM0ElMkYlMkZ3d3cuYXBhcnRtZW50ZGF0YS5 pbyUyRmRhc2hib2FyZCUyRnR4LWhvJTJGY2hhbmdlLXJlcG9ydCZsYW 5kc2NhcGU9dHJ1ZSZkaXNwbGF5SGVhZGVyRm9vdGVyPXRydWUmcHJpb nRCYWNrZ3JvdW5kPXRydWUmc2NhbGU9MSZwYXBlcldpZHRoPTgmcGFw ZXJIZWlnaHQ9MTEmbWFyZ2luVG9wPTAuMiZtYXJnaW5Cb3R0b209MC4 yJm1hcmdpbkxlZnQ9MC4yJm1hcmdpblJpZ2h0PTAuMg=="

What should I do in this situation? Is it because of the ContentType variable sent POST headers http://joxi.ru/RmzLaOBU0e3PKA

Noel Llevares · Accepted Answer · 2018-12-20 19:17:47Z

That is a base64 string.

You can convert that into a Buffer object.

From here you have many options. I recommend the following:

Upload the Buffer object to S3, get the link to S3, and return the link as your output.
Upload the Buffer object to S3, get the link to S3, and return a temporary redirect (302) pointing to that link in S3.
Directly return the Buffer object as a file download.

Collectives™ on Stack Overflow

Postman [POST] request body is not parsing correctly

1 Answer 1

Comments

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Related