-
Notifications
You must be signed in to change notification settings - Fork 8
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
How to parse event.body #1
Comments
Are you deploying using the Serverless framework? |
Yup
…On Fri, Mar 2, 2018 at 5:47 AM Yan Cui ***@***.***> wrote:
Are you deploying using the Serverless framework?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AenvvpVHcd9A_eQroNG5hhWtoJ9q2f-yks5taWmagaJpZM4SZPCY>
.
|
ok, then here are the things you're going to need:
then API Gateway would treat the request body as binary and base64 encode it, you should be able to see this as the If these doesn't work, then maybe point me to a gist of your code so I can see what's going on. Unfortunately the whole setup is still a bit "magic" :-/ |
Thanks for the code example.
I'm trying to setup a gateway that accepts protobuf encoded responses.
It seems like AWS converts the binary payload to a JSON string in event.body?
When I try to decode this, I'm getting errors.
Could you show an example of decoding event.body (https://github.com/theburningmonk/lambda-protobuf-demo/blob/master/functions/proto.js#L10)
The text was updated successfully, but these errors were encountered: