Expected behavior for method and scheme when passed an `other` with a well-known name

Open
#781 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
wasm
Domain
api

Research direction

No file, test, or entry point is named in the issue. Start by reviewing the relevant WASI HTTP API specification and establish the expected behavior for method and scheme values with well-known names, including the case variants; done means the behavior is agreed for all listed inputs.

Written by the indexing model from the issue text.

Description

P-http

What is the expected behavior if we set-method(other("GET")) ? Should it error, or should it resolve to method::get, or stay as other?

Similar for set-scheme(other("https")), but there since schemes are case-insensitive, we should also ask about set-scheme(other("HTTPS")).

Dominant language
Rust
Stars
5.8k
Forks
333
Avg merge
2d 13h
Merged PRs (30d)
3

Contributor guide

Open the contributing guide

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 WebAssembly/WASI

All issues in WebAssembly/WASI

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.