[Triage] P-http backlog sweep

[ricochet]

@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)

• Proposal: an interface for modeling long-running processes for HTTP serving #807 — Proposal: an interface for modeling long-running processes for HTTP serving _{last activity 2025-07, 21 comment(s)}
• HTTP/1.1 request-lines and optionality of scheme & authority #788 — HTTP/1.1 request-lines and optionality of scheme & authority _{last activity 2025-08, 0 comment(s)}
• Forbid non-ascii field names #786 — Forbid non-ascii field names _{last activity 2025-09, 2 comment(s)}
• [v0.3] specify order for fields#get, fields#set #792 — [v0.3] specify order for fields#get, fields#set _{last activity 2025-09, 2 comment(s)}
• [v0.3] Why bother with request-options when asyncs are there? #790 — [v0.3] Why bother with request-options when asyncs are there? _{last activity 2025-09, 2 comment(s)}
• Adding headers with multiple casings of the same field name #787 — Adding headers with multiple casings of the same field name _{last activity 2025-09, 3 comment(s)}
• Why import stdio ports, random, wall-clock, timezone ? #789 — Why import stdio ports, random, wall-clock, timezone ? _{last activity 2025-09, 4 comment(s)}
• Adding an interface to query readiness to accept requests #784 — Adding an interface to query readiness to accept requests _{last activity 2025-09, 4 comment(s)}
• [v0.3] Specify behavior for fields#delete, fields#get-and-delete with invalid field name #783 — [v0.3] Specify behavior for fields#delete, fields#get-and-delete with invalid field name _{last activity 2025-10, 0 comment(s)}
• What is a "HTTP Related Scheme" ? #782 — What is a "HTTP Related Scheme" ? _{last activity 2025-10, 0 comment(s)}
• Expected behavior for method and scheme when passed an other with a well-known name #781 — Expected behavior for method and scheme when passed an other with a well-known name _{last activity 2025-10, 1 comment(s)}
• Specify that percent-encoded domain names are unsupported #778 — Specify that percent-encoded domain names are unsupported _{last activity 2025-10, 1 comment(s)}
• Specify what happens when IPv6 is unavailable #779 — Specify what happens when IPv6 is unavailable _{last activity 2025-10, 4 comment(s)}
• Expected normalization for path-and-query? #780 — Expected normalization for path-and-query? _{last activity 2025-10, 2 comment(s)}
• [v0.3] Expand documentation of "result of transmission" futures #777 — [v0.3] Expand documentation of "result of transmission" futures _{last activity 2025-10, 2 comment(s)}
• Consider extending the proxy world with an origin #793 — Consider extending the proxy world with an origin _{last activity 2025-10, 11 comment(s)}
• DNS error rcode type #785 — DNS error rcode type _{last activity 2025-10, 3 comment(s)}
• Specify range of valid HTTP response codes #849 — Specify range of valid HTTP response codes _{last activity 2025-12, 3 comment(s)}
• [v0.3] Specify what is meant by "not syntactically valid" #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.

• Figure out the right set of cases in error #824 — Figure out the right set of cases in error _{last activity 2023-03, 0 comment(s)}
• Consider optimizations to reduce the number of host calls #823 — Consider optimizations to reduce the number of host calls _{last activity 2023-03, 1 comment(s)}
• Ownership model for streams is not clear. #822 — Ownership model for streams is not clear. _{last activity 2023-03, 5 comment(s)}
• incoming-request-* should return Result<foo> #820 — incoming-request-* should return Result _{last activity 2023-03, 2 comment(s)}
• WASI-http needs a sequence diagram #818 — WASI-http needs a sequence diagram _{last activity 2023-04, 4 comment(s)}
• Expose protocol version #817 — Expose protocol version _{last activity 2023-04, 1 comment(s)}
• Explicit run-server needed? #819 — Explicit run-server needed? _{last activity 2023-05, 5 comment(s)}
• Should outgoing-handler::handle consume its parameter? #816 — Should outgoing-handler::handle consume its parameter? _{last activity 2023-06, 1 comment(s)}
• Fields/Headers take a list of Vec<(String, String)> to create, but probably should take Vec<(String, List<String>)> #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)}
• Versioning/Tagging? #815 — Versioning/Tagging? _{last activity 2023-07, 10 comment(s)}
• Require network handle #814 — Require network handle _{last activity 2023-10, 1 comment(s)}
• outgoing-handler and valid request-options #813 — outgoing-handler and valid request-options _{last activity 2023-10, 2 comment(s)}
• Document content length check is applied to outoing-body output-stream #809 — Document content length check is applied to outoing-body output-stream _{last activity 2023-11, 1 comment(s)}
• outgoing-body flush behaviour states #811 — outgoing-body flush behaviour states _{last activity 2023-11, 3 comment(s)}
• OutgoingBody finish content length errors #810 — OutgoingBody finish content length errors _{last activity 2023-11, 4 comment(s)}
• Proposal: add a fields.keys method. #808 — Proposal: add a fields.keys method. _{last activity 2023-12, 0 comment(s)}
• Methods needed to get owned headers out of requests and responses #806 — Methods needed to get owned headers out of requests and responses _{last activity 2024-02, 8 comment(s)}
• Clarifying abort behaviours #812 — Clarifying abort behaviours _{last activity 2024-03, 2 comment(s)}
• Inconsistency with wasi:http@0.2.0 snapshots #589 — Inconsistency with wasi:http@0.2.0 snapshots _{last activity 2024-03, 1 comment(s)}
• streams are not implemented in wit-bindgen for C bindings #804 — streams are not implemented in wit-bindgen for C bindings _{last activity 2024-04, 1 comment(s)}
• [v0.3] Make (potentially all) headers mutable  #803 — [v0.3] Make (potentially all) headers mutable _{last activity 2024-05, 10 comment(s)}
• [v0.3] Request metadata #825 — [v0.3] Request metadata _{last activity 2024-05, 7 comment(s)}
• Consider adding wasi-runtime-config to proxy world #802 — Consider adding wasi-runtime-config to proxy world _{last activity 2024-07, 2 comment(s)}
• Header Validations #800 — Header Validations _{last activity 2024-08, 2 comment(s)}
• Do you really need 2 different handler interfaces?  #799 — Do you really need 2 different handler interfaces? _{last activity 2024-08, 6 comment(s)}
• [v0.3] Support HTTP Upgrade #797 — [v0.3] Support HTTP Upgrade _{last activity 2024-11, 1 comment(s)}
• Additions to support gRPC #798 — Additions to support gRPC _{last activity 2024-11, 9 comment(s)}
• [v0.3] pass request-options to outgoing-handler by borrow #796 — [v0.3] pass request-options to outgoing-handler by borrow _{last activity 2024-11, 0 comment(s)}
• Support for interim responses (1xx) #801 — Support for interim responses (1xx) _{last activity 2024-12, 15 comment(s)}
• inconsistent future resource ownership #795 — inconsistent future resource ownership _{last activity 2025-01, 5 comment(s)}
• Handling/forwarding error-contexts that can be generated during a body.finish #794 — Handling/forwarding error-contexts that can be generated during a body.finish _{last activity 2025-02, 5 comment(s)}