apache / apache/servicecomb-java-chassis
ServiceComb中处理Content-Length和Transfer-Encoding逻辑
Open
- Dominant language
- Java
- Stars
- 1.9k
- Forks
- 814
- Avg merge
- 8d 23h
- Merged PRs (30d)
- 1
Description
ServiceComb版本2.8.12，下载接口因为有组件依赖Content-Length请求头，在Edge中增加HttpServerFilter中设置Content-Length后Transfer-Encoding请求头没了，通过edge增加accesslog打印Transfer-Encoding为空，想问下ServiceComb中处理Content-Length和Transfer-Encoding逻辑是什么？
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing the Edge HttpServerFilter handling and the access log for the download request in ServiceComb 2.8.12. Reproduce the interaction between Content-Length and Transfer-Encoding, then compare the observed headers with the framework's documented behavior. Done means identifying the relevant processing path and providing a confirmed explanation or a narrowly scoped fix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100