我正在尝试将 Amazon API gateway 与 Lambda 函数集成。我成功地实现了这一目标,但是当我尝试使用curl 时,它失败了。
设置 Lambda 方法、API 网关集成以及集成请求下的模板映射。
当我从控制台运行“测试”时,它工作正常
Execution log for request test-request
Wed Nov 04 07:27:30 UTC 2015 : Starting execution for request: test-invoke-request
Wed Nov 04 07:27:30 UTC 2015 : API Key: test-invoke-api-key
Wed Nov 04 07:27:30 UTC 2015 : Method request path: {service=xml}
Wed Nov 04 07:27:30 UTC 2015 : Method request query string: {}
Wed Nov 04 07:27:30 UTC 2015 : Method request headers: {}
Wed Nov 04 07:27:30 UTC 2015 : Method request body before transformations: Articletext
Wed Nov 04 07:27:30 UTC 2015 : Endpoint request body after transformations: {
"prog" : "xml",
"content" : "Articletext",
"test" : "{path={service=xml}, querystring={}, header={}}"
}
但是当我尝试通过卷曲访问它时,它无法在转换后创建正确的主体
卷曲-X POSThttps://aaaaaaa.execute-api.us-west-2.amazonaws.com/beta/apitest/xml-H“内容类型:application/x-www-form-urlencoded;字符集=UTF-8”--data-binary“Articletext”
Starting execution for request:
Method request path: {service=xml}
Method request query string:
{}
Method request body before transformations: Articletext
Endpoint request body after transformations: Articletext
Endpoint response body before transformations:
{
"Type": "User",
"message": "Could not parse request body into json."
}
任何人都可以建议我有关缺失部分的问题吗?
就我而言,问题是我没有部署 API,因此它没有更新以供外部使用。
看Amazon API Gateway:通过 Postman 调用 API 时,响应正文未转换?
本文内容由网友自发贡献,版权归原作者所有,本站不承担相应法律责任。如您发现有涉嫌抄袭侵权的内容,请联系:hwhale#tublm.com(使用前将#替换为@)