使用 AWS re:Post 即表示您同意 AWS re:Post 使用條款
AWS re:Postre:Post

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

0

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?

主題
無伺服器應用程式整合
標籤
無伺服器AWS Step Functions
語言
English
Siggi
已提問 3 個月前檢視次數 186 次
1 個回答
-1
  • 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

profile picture
專家
Giovanni Lauria
已回答 3 個月前
  • Siggi
    3 個月前

    Thanks for the reply, but I didn't ask what those headers are. I'm well aware of it. My question is why they use "Transfer-Encoding: chunked" as they know the payload in advance. It is the input of the task and smaller than 256kb. Whenever we know the size in advance it makes way more sense to use the Content-Length approach. I hope the request gets somehow forwarded to the StepFunction team.

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋，同時有助於提問者的專業成長。

回答問題指南

相關內容