Invalid characters in scheme give wrong error about trurl HOT 2 CLOSED

The ones where you set the scheme only should at least give a better error.

The ones that set the URL are more difficult:

Since a scheme can only be alphanumerical, something like ht<p://example.com is treated as a scheme-less URL, so ht<p (before the hostname characters are valided) is an attempted hostname but what follows the host name is a colon without a port number, which is illegal. I'm sure this can be improved, probably for example by checking the host name to be valid before it checks (and erroring out because of) the port number.

At least the full URL ones are a curl issue, possible the first ones are as well.

from trurl.

I think we just have to accept this for the time being unless someone can figure out a clever way to improve this...

from trurl.