-
Notifications
You must be signed in to change notification settings - Fork 2.4k
Fix malformed response in example #1089
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Release/v1.13.1
The required `isBase64Encoded` field was missing, and `headers` was not correctly formatted. This fixes the "Malformed Lambda proxy response" that caused the method to fail with a 502 status. Some additional information here: https://aws.amazon.com/premiumsupport/knowledge-center/malformed-502-api-gateway/
Codecov Report
@@ Coverage Diff @@
## master #1089 +/- ##
=======================================
Coverage 94.87% 94.87%
=======================================
Files 69 69
Lines 3161 3161
Branches 603 603
=======================================
Hits 2999 2999
Misses 84 84
Partials 78 78 Continue to review full report at Codecov.
|
@kennyk Thanks for this contribution! PRs should be made against the |
@jlhood I think it'll be easier to just re-fork and open a new PR. Will do that. |
Now here: |
Description of changes:
The required
isBase64Encoded
field was missing, andheaders
was not correctly formatted. This fixes the "Malformed Lambda proxy response" that caused the method to fail with a 502 status.Some additional information here:
https://aws.amazon.com/premiumsupport/knowledge-center/malformed-502-api-gateway/
Description of how you validated changes:
I have first created a
Function
with the javascript in this example, and got the502
. I have then made changes according to the documentation above, and now the correct redirect is returned.Checklist:
make pr
passesexamples/2016-10-31
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.