AWS StepFunction HTTP Invoke. Transfer-Encoding: chunked vs Content-Length

Question

I see that the HTTP Invoke Task from StepFunctions uses "Transfer-Encoding: chunked" and streams data to the 3rd party.
Why is that so? Afaik it's way better to use the more adopted way of setting the Content-Length as we already know the size of the content in advance anyway. 
Could you please support that, or do you have it in your roadmap to implement?

Giovanni Lauria · Answer

* Transfer-Encoding: chunked is used when the size of the content is not known in advance or is dynamically generated. This allows the sender to start transmitting dynamically generated content before knowing the total size, which can be beneficial for large files or streams.
* On the other hand, Content-Length is used when the size of the content is known in advance. It allows the receiver to know the exact size of the content that will be received, which can be useful for progress tracking and resource allocation.

I do not have hold of any roadmap

AWS StepFunction HTTP Invoke. Transfer-Encoding: chunked vs Content-Length

相关内容