Re: [whatwg/url] Confusion about pipe characters in paths (Issue #852)

I still don't understand.

- `valid URL string` does not permit pipes.
- Browsers send pipes as URLs anyway (or are supposed to), when the HTML says so.
- when using the `basic URL parser`, the URL will produce an `invalid-URL-unit` error, because pipe is not in `URL units`.

How does this mesh? You're saying not to percent-encode pipes on the URL encoding side, but at the same time, you're telling parsers not to accept unencoded pipes.

Is this just a HTML-specific quirk? You're saying URLs normally shouldn't include pipes, but if a HTML document has an unencoded pipe in a link, we should assume the server URL parser is out-of-spec and accepts it, so we should send it as-is? That would make sense from a whatwg standpoint (since you are concerned with HTML / browsers specifically), but it apparently leads to insufficient escaping for non-HTML applications that use your URL encoding sets.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/url/issues/852#issuecomment-2609160130
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/url/issues/852/2609160130@github.com>