Restrict / review `Transfer-Encoding` header rendering · akka/akka-http#3761

(0 评论) (0 反应) (0 负责人)Scala (1,311 star) (598 fork)batch import

1 - triageddiscusshackathonhelp wantedt:coret:model

描述

Since #3754, we only support Transfer-Encoding: chunked headers and no other ones. The reasoning is that akka-http is implementing the "Transfer" part of HTTP. Leaving parsing or providing custom Transfer-Encoding headers open to the user will lead to confusion and bugs.

We should check that:

The Transfer-Encoding model could make sure that the latest entry is always chunked (see RFC), though that would change the error reporting for parsing as now implemented with #3754
User-provided Transfer-Encoding headers will always be ignored

贡献者指南

技术栈: 无
领域: backendapi
议题类型: feature
难度: 3
预计时间: 1-2 days
活动状态: stale
清晰度: mostly clear
前置要求: HTTP Transfer Encoding knowledgeakka http internals
新手友好度: 25
研究方向: Investigate the current implementation from PR #3754 to understand how Transfer Encoding headers are parsed and rendered. The goal is to restrict the model so that only 'chunked' is allowed and user provided headers are ignored. Look at the HttpHeader model and the rendering code to add validation. The issue mentions two checks: ensuring the latest entry is always 'chunked' and ignoring user provided headers. Consider how to integrate these without breaking existing error handling.