通过 API 网关在 aws Lambda 中获取 json 正文 [英] Getting json body in aws Lambda via API gateway

问题描述

我目前正在使用 NodeJS 通过 AWS Api Gateway 在 AWS lambda 上构建机器人，但我遇到了 POST 请求和 JSON 数据的问题.我的 api 使用使用 Lambda 代理集成"，即使我测试代理发送 Application/json 的内容类型和正文中的一些 json 例如 {"foo":"bar"} 我可以'不先解析就访问对象

I'm currently using NodeJS to build a bot on AWS lambda via AWS Api Gateway and I'm running into an issue with POST requests and JSON data. My api uses 'Use Lambda Proxy integration' and even when I test the proxy sending a content-type of Application/json and some json in the body e.g {"foo":"bar"} I can't access the object without parsing it first

例如

  var json = JSON.parse(event.body);
  console.log(json.foo);

现在我知道仅仅通过 JSON.parse 运行它似乎没什么大不了的，但我已经看到了许多其他示例，但事实并非如此.见这里 https://github.com/pinzler/fb-messenger-bot-aws-lambda/blob/master/index.js

Now I know this doesn't seem a big deal just running it through JSON.parse, but I've seen a number of other examples where this isn't the case at all. see here https://github.com/pinzler/fb-messenger-bot-aws-lambda/blob/master/index.js

我是否需要向 API 网关添加任何内容才能正确处理此问题?我在发布方法请求"部分中的请求正文"步骤为请求正文设置了 application/json 的内容类型.

Do I need to add anything to my API gateway to handle this correctly? my 'request body' step in the 'post method request' section has a content-type of application/json set-up for the request body.

就我所知，上面示例的自述文件似乎没有使用代理集成，所以我不确定我应该在这里做什么

The readme for the example above doesn't seem to use proxy integration as far as I can tell so I'm not sure what I should be doing here

推荐答案

您可以在 API Gateway 中配置两种不同的 Lambda 集成，例如 Lambda 集成和 Lambda 代理集成.对于Lambda 集成，您可以自定义您将在不需要解析正文的有效负载中传递给 Lambda 的内容，但是当您使用 Lambda 代理集成 在 API Gateway 中，API Gateway 会像这样将负载中的所有内容代理到 Lambda，

There are two different Lambda integrations you can configure in API Gateway, such as Lambda integration and Lambda proxy integration. For Lambda integration, you can customise what you are going to pass to Lambda in the payload that you don't need to parse the body, but when you are using Lambda Proxy integration in API Gateway, API Gateway will proxy everything to Lambda in payload like this,

{
    "message": "Hello me!",
    "input": {
        "path": "/test/hello",
        "headers": {
            "Accept": "text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8",
            "Accept-Encoding": "gzip, deflate, lzma, sdch, br",
            "Accept-Language": "en-US,en;q=0.8",
            "CloudFront-Forwarded-Proto": "https",
            "CloudFront-Is-Desktop-Viewer": "true",
            "CloudFront-Is-Mobile-Viewer": "false",
            "CloudFront-Is-SmartTV-Viewer": "false",
            "CloudFront-Is-Tablet-Viewer": "false",
            "CloudFront-Viewer-Country": "US",
            "Host": "wt6mne2s9k.execute-api.us-west-2.amazonaws.com",
            "Upgrade-Insecure-Requests": "1",
            "User-Agent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.82 Safari/537.36 OPR/39.0.2256.48",
            "Via": "1.1 fb7cca60f0ecd82ce07790c9c5eef16c.cloudfront.net (CloudFront)",
            "X-Amz-Cf-Id": "nBsWBOrSHMgnaROZJK1wGCZ9PcRcSpq_oSXZNQwQ10OTZL4cimZo3g==",
            "X-Forwarded-For": "192.168.100.1, 192.168.1.1",
            "X-Forwarded-Port": "443",
            "X-Forwarded-Proto": "https"
        },
        "pathParameters": {"proxy": "hello"},
        "requestContext": {
            "accountId": "123456789012",
            "resourceId": "us4z18",
            "stage": "test",
            "requestId": "41b45ea3-70b5-11e6-b7bd-69b5aaebc7d9",
            "identity": {
                "cognitoIdentityPoolId": "",
                "accountId": "",
                "cognitoIdentityId": "",
                "caller": "",
                "apiKey": "",
                "sourceIp": "192.168.100.1",
                "cognitoAuthenticationType": "",
                "cognitoAuthenticationProvider": "",
                "userArn": "",
                "userAgent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.82 Safari/537.36 OPR/39.0.2256.48",
                "user": ""
            },
            "resourcePath": "/{proxy+}",
            "httpMethod": "GET",
            "apiId": "wt6mne2s9k"
        },
        "resource": "/{proxy+}",
        "httpMethod": "GET",
        "queryStringParameters": {"name": "me"},
        "stageVariables": {"stageVarName": "stageVarValue"},
        "body": "{"foo":"bar"}",
        "isBase64Encoded": false
    }
}

对于您引用的示例，它没有从原始请求中获取正文.它正在将响应主体构造回 API 网关.应该是这种格式，

For the example you are referencing, it is not getting the body from the original request. It is constructing the response body back to API Gateway. It should be in this format,

{
    "statusCode": httpStatusCode,
    "headers": { "headerName": "headerValue", ... },
    "body": "...",
    "isBase64Encoded": false
}

这篇关于通过 API 网关在 aws Lambda 中获取 json 正文的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！