Re: [whatwg/url] A '@' character in the host part of file URLs (Issue #805)

Oh I see, that is indeed confusing.

I was thinking that we probably want to switch `file:` URLs to use opaque hosts instead of domains (for which #599 is the issue) as that would also allow percent-encoding of `@`, for instance and address other issues outlined in #599.

Now for non-percent-encoded spaces do they need to remain non-percent-encoded or would it be okay when we create the buffer which we pass to the host parser to percent-encode at that point? That way opaque hosts can still ban spaces, but they end up working for `file:` URLs due to preprocessing in the "file host state".

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

Message ID: <whatwg/url/issues/805/2510953302@github.com>