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

`IfMatch` of empty string doesn't get rejected as expected

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

Nobody has claimed this yet.

Assessment

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

Research direction

Start by reproducing the issue with the headers::IfMatch::decode example in the report and compare its behavior with ETag decoding. Trace the IfMatch decoder and its empty-input handling; done means an empty HeaderValue is rejected consistently with the expected error behavior.

Written by the indexing model from the issue text.

Description

I wouldn't expect this to pass. It doesn't for ETag but it seems to work for IfMatch for some reason

use headers::Header as _;

fn main() {
    let _ = headers::IfMatch::decode(&mut [&headers::HeaderValue::from_static("")].into_iter())
        .unwrap();
    let _ = headers::IfMatch::decode(&mut [].into_iter()).unwrap();
}
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.