lostisland/faraday

Please revisit the comma separated header collapsing decision.

Open

#1,120 创建于 2020年1月22日

在 GitHub 查看
 (6 评论) (1 反应) (0 负责人)Ruby (5,861 star) (997 fork)batch import
featurehelp wanted

描述

There was a decision to concatenate multiple header values using comma as a delimiter in the past. (https://github.com/lostisland/faraday/issues/44) And this is the real-world consequences of the decision. https://github.com/sparklemotion/http-cookie/issues/28

Could you somehow provide a way to access raw HTTP headers?

贡献者指南

技术栈
无
领域
apibackend
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
half day
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
familiarity with faraday middlewareunderstanding of HTTP header concatenation
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
45
研究方向
Review the historical decision in issue #44 where header concatenation was chosen. Examine the current header handling code in Faraday's Response or middleware, particularly how headers are stored and accessed. Look at the external http cookie issue to understand real world impact. Consider implementing a method to expose raw headers (e.g., `response.raw headers`) that returns headers as a hash of arrays. Check if any existing PRs or discussions address this.
Please revisit the comma separated header collapsing decision. · lostisland/faraday#1120 | Good First Issue