Re: [whatwg/url] [Editorial] Guarantee that strings encoded with the component encode-set are valid opaque host strings. (#584)

@karwa commented on this pull request.



> @@ -205,7 +205,7 @@ U+0024 ($) to U+0026 (&), inclusive, U+002B (+), and U+002C (,).
 <p class=note>This is used by <cite>HTML</cite> for
 {{NavigatorContentUtils/registerProtocolHandler()}}, and could also be used by other standards to
 percent-encode data that can then be embedded in a <a for=/>URL</a>'s <a for=url>path</a>,
-<a for=url>query</a>, or <a for=url>fragment</a>. Using it with
+<a for=url>query</a>, or <a for=url>fragment</a>, and is also a <a>valid opaque-host string</a>. Using it with

Sure, that's good - I like how it now says "embedded ... in an opaque host" and not just "is a valid opaque host".

As for `%`, it says a valid opaque-host string is made of URL Units, which are URL code points (doesn't include `%`) and percent-encoded bytes (which do of course include `%`), so I think it's implied that `%` is fine, but _only_ when used for percent-encoding, and not just generally as part of the host's name.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/url/pull/584#discussion_r586311712

Received on Wednesday, 3 March 2021 10:48:54 UTC