-
Notifications
You must be signed in to change notification settings - Fork 671
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
Fix: content-length was not matching the body after an array to string conversion #130
Fix: content-length was not matching the body after an array to string conversion #130
Conversation
Is this causing an issue? Is this the right thing to do? API Gateway converts it again anyway, and at that point the content-length will not match the content that gets returned to the client. |
@brettstack It is causing issues if you run your code locally using https://github.com/awslabs/aws-sam-local I could not find a good workaround. What do you think? |
Sounds like a SAM Local issue. Do they have binary support? If they don't then it will just result in a base64 string being returned, right? |
Merged in #147 which fixes this. Thanks! |
<a name="3.3.5"></a> ## [3.3.5](CodeGenieApp/serverless-express@v3.3.4...v3.3.5) (2018-08-20) ### Bug Fixes * apply Content-Length header when missing ([b0927b8](CodeGenieApp/serverless-express@b0927b8)), closes [#147](CodeGenieApp/serverless-express#147) [#106](CodeGenieApp/serverless-express#106) [#130](CodeGenieApp/serverless-express#130) * apply Content-Length header when missing ([#175](CodeGenieApp/serverless-express#175)) ([c2f416b](CodeGenieApp/serverless-express@c2f416b))
Issue: #129
Description of changes:
Recalculate the body length and set the content-length with this new value.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.