Remove "transfer-encoding" header from responses #442
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bnusunny
changed the title
mbfreder
approved these changes
Apr 19, 2024
bnusunny
changed the title
|
I need to double check if this is the right place to remove these headers. At least 'transfer-encoding' is used in lambda-http crate to handle response body. |
bnusunny
changed the title
bnusunny
changed the title
|
I confirmed 'transfer-encoding' is not used in lambda-http crate to handle response body. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of changes:
This change removes "transfer-encoding" http header from web app response. This resolves an issue that
sam local start-apifails to handle the chunked response from SpringBoot.By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.