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

`IfNoneMatch::decode()` returns and empty `ETag` even if the iterator passed to it is empty

Open
#204 0 comments 5 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 at the IfNoneMatch::decode entry point and reproduce the behavior with the empty-iterator test shown in the issue. Trace how an empty iterator is handled, then verify that an empty input returns an error and that valid If-None-Match values still decode successfully.

Written by the indexing model from the issue text.

Description

use headers::{IfNoneMatch, Header};

#[test]
fn test_empty_if_none_match() {
    let mut iter = std::iter::empty();
    let if_none_match = IfNoneMatch::decode(&mut iter);

    assert!(if_none_match.is_err()); // This assert fails. `decode` returns `Ok(IfNoneMatch(Tags("")))`
}

This means that even if there's no IfNoneMatch header in the request, this'll still report it as present.

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.