Skip to content

Conversation

kennyk
Copy link
Contributor

@kennyk kennyk commented Aug 16, 2019

Description of changes:
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/

Description of how you validated changes:
I have first created a Function with the javascript in this example, and got the 502. I have then made changes according to the documentation above, and now the correct redirect is returned.

Checklist:

  • Write/update tests
  • make pr passes
  • Update documentation
  • Verify transformed template deploys and application functions as expected
  • Add/update example to examples/2016-10-31

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@codecov-io
Copy link

codecov-io commented Aug 16, 2019

Codecov Report

Merging #1089 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           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.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e7c4117...f97aac8. Read the comment docs.

@kennyk kennyk marked this pull request as ready for review August 16, 2019 12:09
@kennyk kennyk changed the title Fix malformed response Fix malformed response in example Aug 16, 2019
@praneetap praneetap changed the base branch from master to develop August 16, 2019 18:01
@jlhood
Copy link
Contributor

jlhood commented Aug 19, 2019

@kennyk Thanks for this contribution! PRs should be made against the develop branch, not master. We've changed the base branch on this PR to develop, but now there are a lot of conflicts. Can you rebase your changes onto the develop branch and re-push so only your change shows up in the diff?

@kennyk kennyk closed this Aug 22, 2019
@kennyk kennyk deleted the master branch August 22, 2019 16:10
@kennyk kennyk restored the master branch August 22, 2019 16:14
@kennyk
Copy link
Contributor Author

kennyk commented Aug 22, 2019

@jlhood I think it'll be easier to just re-fork and open a new PR. Will do that.

@kennyk
Copy link
Contributor Author

kennyk commented Aug 22, 2019

Now here:
#1096

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants