nodejs/node

No content length on DELETE and OPTIONS

Open

#27,880 创建于 2019年5月26日

在 GitHub 查看
 (26 评论) (0 反应) (0 负责人)JavaScript (117,218 star) (35,535 fork)batch import
confirmed-bughelp wantedhttp

描述

Looking through https://github.com/nodejitsu/node-http-proxy/commit/8a24a1e18f384d29a125eda1d2311bdd8ec66871 and reading through the node code. I do believe we have an unhandled case.

I believe we are missing something here: https://github.com/nodejs/node/blob/master/lib/_http_outgoing.js#L349

To ensure content-length and transfer-encoding are correct.

Am I on to something or should I drop this?

贡献者指南

技术栈
javascriptnodejs
领域
backendapi
议题类型
bug
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-3 hours
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
needs investigation
前置要求
HTTP protocol basicsNode.js HTTP module internals
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
35
研究方向
Investigate the referenced commit (8a24a1e) and the http outgoing.js file, specifically around line 349. Determine if DELETE and OPTIONS methods should set content length or transfer encoding headers. Check Node.js HTTP spec compliance. Review the 26 comments for any conclusions or proposed fixes.