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

Access-Control-Request-Headers should not use a space when combining

Open
#207 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
50/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
rust
Domain
networking

Research direction

Inspect the Rust implementation of the Access-Control-Request-Headers value and compare its joining behavior with the Fetch CORS specification and the linked web-platform-tests test. Done means header names are joined with commas only, without spaces, and the strict WPT case passes.

Written by the indexing model from the issue text.

Description

easy

The Fetch CORS spec specifically notes that the header list that is the value of ACRH does not use combine and only uses , (comma) to join the header names.

MDN's example value for this header also does not use spaces.

The WPT test https://github.com/web-platform-tests/wpt/blob/master/xhr/resources/access-control-preflight-request-header-sorted.py tests for this strictly.

Dominant language
Rust
Stars
200
Forks
107
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 hyperium/headers

All issues in hyperium/headers

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.