Pseudo-header fields in trailers are silently discarded
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- rust
- Domain
- networking
Research direction
Start by tracing how trailer fields pass through into_fields() and how the receive side handles recv_close(). Check the stream-state handling for unexpected HEADERS after END_STREAM so existing errors, including GOAWAY, remain unchanged. Done means pseudo-header fields in trailers produce RST_STREAM(PROTOCOL_ERROR) while receiving, with existing stream-state errors preserved.
Written by the indexing model from the issue text.
Description
Trailer pseudo-header fields are silently discarded by into_fields(), allowing malformed messages to complete successfully. RFC 9113 Section 8.3 forbids pseudo-headers in trailers. Validate them before recv_close() and conversion, returning RST_STREAM(PROTOCOL_ERROR) while the receive side is streaming. Preserve existing stream-state errors otherwise, including GOAWAY for unexpected HEADERS after END_STREAM.
- Dominant language
- Rust
- Stars
- 1.6k
- Forks
- 395
- Avg merge
- 6h 3m
- Merged PRs (30d)
- 8
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from hyperium/h2
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
Maintainers usually reply within 1 day
-
Raw fragments in :path are discarded before request-target validationPossibly taken @cfal claimed this 2 days ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 20/100
Maintainers usually reply within 1 day
-
Oversized trailers bypass max_header_list_size and are silently truncatedPossibly taken @cfal claimed this 2 days ago. Open
Difficulty 4/5 3-5 days Newbie friendliness 20/100
Maintainers usually reply within 1 day
-
Trailers after a chained DATA frame always cost a second writePossibly taken @koshea claimed this 9 days ago. Open
Difficulty 4/5 3-5 days Newbie friendliness 30/100
Maintainers usually reply within 1 day
-
Receive flow-control stall after SETTINGS ACK shrinks the window with previously released capacityOpen
Difficulty 3/5 1-2 days Newbie friendliness 50/100
hyperium/h2#976 · 1 reaction ·
Maintainers usually reply within 1 day
Similar issues
-
`image_generation`: `max_retries` is ignored for OpenAI-compatible providers (always 2 retries)Possibly taken @ericz7900 claimed this today. Openllm translation
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 1 day
-
Help-Wanted Needs-Triage Package-Request
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
microsoft/winget-pkgs#456324 ·
Maintainers usually reply within 1 day
-
ai_p2
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
ClickHouse/ClickHouse#126833 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
area/runtime good first issue size/S type/refactor
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
lorica-labs/volant#681 ·
Maintainers usually reply within 1 day