Re: [whatwg/url] Web compatibility issue with various unknown (external) protocols like ed2k (Issue #815)

I think there are two different issues with these schemes.
1. Schemes that wrap another URL with the intention of passing that URL to an external protocol handler.
2. Schemes such as `ed2k` which have a totally different definition. Even with RFC 3986 rules `ed2k://|file|The_Two_Towers-The_Purist_Edit-Trailer.avi|14997504|965c013e991ee246d63d45ea71954c4d|/
` is not a valid URI as `|` is not a valid host character, but as it happens it used to work. The question is how much effort should we expend in keeping these URLs functioning on the web?

While I don't have any experience with `ed2k` I think it's also supposed to be passed to an external protocol handler. But that doesn't work unless it's successfully parsed.



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

Message ID: <whatwg/url/issues/815/1914612736@github.com>