Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

case insensitive headers

Open
#91 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript
Domain
networking

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.

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

Dominant language
JavaScript
Stars
245
Forks
104
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from browserify/http-browserify

All issues in browserify/http-browserify

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.