Specify that percent-encoded domain names are unsupported

Open
#778 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
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
rust, wasm
Domain
networking

Research direction

Start by reviewing RFC9110 §3.2.2 and the %78.com example, then compare the repository's relevant authority-handling rules with wasmtime's behavior. Done means the applicable specification clearly states how percent-encoded domain names are handled and the resulting behavior is consistent.

Written by the indexing model from the issue text.

Description

P-http

If I go to %78.com in the browser, that takes me to x.com. Indeed in RFC9110 §3.2.2, percent-encoding is allowed in HTTPS authorities:

      reg-name    = *( unreserved / pct-encoded / sub-delims )

But, let's just save ourselves the trouble and forbid percent-encoding in domain names. FWIW, wasmtime fails if the host part of an authority has a %.

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.