-
Notifications
You must be signed in to change notification settings - Fork 231
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
isBase64Encoded field missing from APIGatewayProxyResponseEvent #46
Comments
I'm facing the same issue. Also, I miss the |
I've overlooked the request object. Indeed, the |
Please can this be merged... |
merged #48 |
I've juste created a lambda returning application/pdf data encoded as base64.
In the api gateway logs, I cannot see anywhere isBase64Encoded in the response received from lambda. Where is it supposed to be set ? My client keeps receiving response from api gateway as base64 encoded string. I would like the data to be sent as binary data. The Accept header sent by my client contains "application/pdf" as the only one parameters and the mediaType in setting of the api gateway is also "application/pdf" (ven tried it with /). Could you help ? |
Co-authored-by: Daniel Torok <torokd@amazon.com>
The field
isBase64Encoded
from https://docs.aws.amazon.com/apigateway/latest/developerguide/set-up-lambda-proxy-integrations.html#api-gateway-simple-proxy-for-lambda-output-format is not present in APIGatewayProxyResponseEvent.It's present in the AwsProxyResponse class from https://github.com/awslabs/aws-serverless-java-container though -- also an Amazon project. Maybe these two projects could share API Gateway data types?
The text was updated successfully, but these errors were encountered: