browserify / browserify/http-browserify
case insensitive headers
- Dominant language
- JavaScript
- Stars
- 245
- Forks
- 104
- PR merge metrics
- No merged PRs in 30d
Description
I understand HTTP header names are case-insensitive (RFC 2616). I'm currently interacting with an API that does not follow protocol, it works via node's https but not browserify's.
If you want complete compatibility with node, I'd say remove the case insensitivity. Otherwise, if you want to just follow the spec, I understand.
In the meantime, I've been able to get my API working, by modifying the browserify source code to remove the tolowercase for the headers
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the Browserify source code that lowercases header names and compare its behavior with Node's https implementation. Clarify whether compatibility with the nonconforming API or RFC-compliant case-insensitive headers is required, then add focused coverage for the chosen behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100