WebAssembly / WebAssembly/WASI
[Triage] P-http backlog sweep
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 5.8k
- Forks
- 333
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 3
Description
@WebAssembly/wasi-http-champions, this is the P-http triage queue for our ongoing backlog sweep.
There are 50 open P-http issues with no activity in the last 6 months. Rather than comment on each one individually, they're collected here as one queue you can work through at your own pace. Nothing on this list is closed automatically, and nothing needs to happen before any particular meeting.
For each item, pick one: keep (a short note in the issue would be helpful), close, or needs the subgroup (flag it and put on a meeting agenda).
Stalled 6–18 months, 19 issue(s)
- #807 — Proposal: an interface for modeling long-running processes for HTTP serving last activity 2025-07, 21 comment(s)
- #788 — HTTP/1.1 request-lines and optionality of scheme & authority last activity 2025-08, 0 comment(s)
- #786 — Forbid non-ascii field names last activity 2025-09, 2 comment(s)
- #792 — [v0.3] specify order for fields#get, fields#set last activity 2025-09, 2 comment(s)
- #790 — [v0.3] Why bother with
request-optionswhen asyncs are there? last activity 2025-09, 2 comment(s) - #787 — Adding headers with multiple casings of the same field name last activity 2025-09, 3 comment(s)
- #789 — Why import stdio ports, random, wall-clock, timezone ? last activity 2025-09, 4 comment(s)
- #784 — Adding an interface to query readiness to accept requests last activity 2025-09, 4 comment(s)
- #783 — [v0.3] Specify behavior for fields#delete, fields#get-and-delete with invalid field name last activity 2025-10, 0 comment(s)
- #782 — What is a "HTTP Related Scheme" ? last activity 2025-10, 0 comment(s)
- #781 — Expected behavior for method and scheme when passed an
otherwith a well-known name last activity 2025-10, 1 comment(s) - #778 — Specify that percent-encoded domain names are unsupported last activity 2025-10, 1 comment(s)
- #779 — Specify what happens when IPv6 is unavailable last activity 2025-10, 4 comment(s)
- #780 — Expected normalization for path-and-query? last activity 2025-10, 2 comment(s)
- #777 — [v0.3] Expand documentation of "result of transmission" futures last activity 2025-10, 2 comment(s)
- #793 — Consider extending the
proxyworld with anoriginlast activity 2025-10, 11 comment(s) - #785 — DNS error rcode type last activity 2025-10, 3 comment(s)
- #849 — Specify range of valid HTTP response codes last activity 2025-12, 3 comment(s)
- #791 — [v0.3] Specify what is meant by "not syntactically valid" last activity 2026-02, 9 comment(s)
Dormant over 18 months - 31 issue(s)
These are already labeled S-inactive.
- #824 — Figure out the right set of cases in
errorlast activity 2023-03, 0 comment(s) - #823 — Consider optimizations to reduce the number of host calls last activity 2023-03, 1 comment(s)
- #822 — Ownership model for streams is not clear. last activity 2023-03, 5 comment(s)
- #820 — incoming-request-* should return Result last activity 2023-03, 2 comment(s)
- #818 — WASI-http needs a sequence diagram last activity 2023-04, 4 comment(s)
- #817 — Expose protocol version last activity 2023-04, 1 comment(s)
- #819 — Explicit
run-serverneeded? last activity 2023-05, 5 comment(s) - #816 — Should
outgoing-handler::handleconsume its parameter? last activity 2023-06, 1 comment(s) - #821 — Fields/Headers take a list of Vec<(String, String)> to create, but probably should take Vec<(String, List)> last activity 2023-06, 14 comment(s)
- #815 — Versioning/Tagging? last activity 2023-07, 10 comment(s)
- #814 — Require network handle last activity 2023-10, 1 comment(s)
- #813 — outgoing-handler and valid request-options last activity 2023-10, 2 comment(s)
- #809 — Document content length check is applied to outoing-body output-stream last activity 2023-11, 1 comment(s)
- #811 — outgoing-body flush behaviour states last activity 2023-11, 3 comment(s)
- #810 — OutgoingBody finish content length errors last activity 2023-11, 4 comment(s)
- #808 — Proposal: add a
fields.keysmethod. last activity 2023-12, 0 comment(s) - #806 — Methods needed to get owned headers out of requests and responses last activity 2024-02, 8 comment(s)
- #812 — Clarifying abort behaviours last activity 2024-03, 2 comment(s)
- #589 — Inconsistency with wasi:http@0.2.0 snapshots last activity 2024-03, 1 comment(s)
- #804 — streams are not implemented in
wit-bindgenfor C bindings last activity 2024-04, 1 comment(s) - #803 — [v0.3] Make (potentially all) headers mutable last activity 2024-05, 10 comment(s)
- #825 — [v0.3] Request metadata last activity 2024-05, 7 comment(s)
- #802 — Consider adding wasi-runtime-config to proxy world last activity 2024-07, 2 comment(s)
- #800 — Header Validations last activity 2024-08, 2 comment(s)
- #799 — Do you really need 2 different handler interfaces? last activity 2024-08, 6 comment(s)
- #797 — [v0.3] Support HTTP Upgrade last activity 2024-11, 1 comment(s)
- #798 — Additions to support gRPC last activity 2024-11, 9 comment(s)
- #796 — [v0.3] pass
request-optionstooutgoing-handlerbyborrowlast activity 2024-11, 0 comment(s) - #801 — Support for interim responses (1xx) last activity 2024-12, 15 comment(s)
- #795 — inconsistent future resource ownership last activity 2025-01, 5 comment(s)
- #794 — Handling/forwarding
error-contexts that can be generated during abody.finishlast activity 2025-02, 5 comment(s)
Contributor 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.
Research direction
Review the issue entries listed in this triage queue, starting with the unchecked items and their existing comment threads. For each issue, determine whether to keep it, close it, or flag it for the subgroup and meeting agenda; done means every queued item has an explicit disposition.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- wasm
- Domain
- api, networking
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100