lostisland/faraday

Please revisit the comma separated header collapsing decision.

Open

#1,120 opened on Jan 22, 2020

View on GitHub
 (6 comments) (1 reaction) (0 assignees)Ruby (997 forks)batch import
featurehelp wanted

Repository metrics

Stars
 (5,861 stars)
PR merge metrics
 (Avg merge 53m) (3 merged PRs in 30d)

Description

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?

Contributor guide

Research direction
Analyze the decision in issue #44 and the linked http cookie issue, then propose a method to expose raw headers while maintaining backward compatibility.
Tech stack
ruby
Domain
backend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitRubyHTTP basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70