Re: [whatwg/url] All the other network schemes (#241)

> Scheme-specific processing generally shouldn't happen in the URL parser

No, you're right that it shouldn't and it goes off topic for this issue, as we've already reached a good conclusion on this, but...

For example, this URL spec goes into exact detail how to parse the 'userinfo' part ([section 3.2.1 in RFC3986](https://tools.ietf.org/html/rfc3986#section-3.2.1)) while schemes such as pop (RFC 2384) and imap (RFC 5092) are very clearly *not* parsed the same way as http/ftp there. I'm thinking primarily of the `;auth=` thing they have.

So, a truly scheme-agnostic spec could say that everything until the '@' is the userinfo part that is treated in a scheme-specific way, and then describe how these particular schemes parse it. Since @ isn't treated as a userinfo and hostname separator anymore, it is a bit complicated.

-- 
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/issues/241#issuecomment-278937343