Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Chunked transfer encoding
See original GitHub issueHi,
I use an express middleware that set to chunked the transfer-encoding headers
'transfer-encoding': 'chunked'
In that case, I get the following error :
The request could not be satisfied. CloudFront attempted to establish a connection with the origin, but either the attempt failed or the origin closed the connection.
To make my request works, in the forwardResponseToApiGateway function of the aws-serverless-express/index.js file I remove this header.
Do you think you could make chunked transfert encoding pass ?
Issue Analytics
- State:
- Created 7 years ago
- Comments:8
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@abhigna I think the
transfer-encoding: chunkedissue still exists. I’ve tried to useaws-serverless-expresswithgraphql-server-expresstoday and I run into the same issue as @denneulinChunked encoding still isn’t working, but we are now deleting the header for you https://github.com/awslabs/aws-serverless-express/commit/4d54a81b831eca97524f15b72fa8be379c80aedb#diff-168726dbe96b3ce427e7fedce31bb0bcR54