Wget2 should complain about unknown URI schemes
Created by: juaristi
This was initially misleading for me:
$ src/wget2 ftp://ftp.debian.org
Failed to open /home/aja/.wgetrc
And I know that FTP is not supported, I was just playing around. But other people maybe don't know it, or they might have mistyped the scheme.
$ src/wget2 hrrp://ftp.debian.org
Failed to open /home/aja/.wgetrc
If I mistype the host name, I know that I have done something wrong:
$ src/wget2 http://ftp.debian.omg
Failed to open /home/aja/.wgetrc
[0] Downloading 'http://ftp.debian.omg' ...
Failed to resolve ftp.debian.omg:80 (Name or service not known)
Failed to resolve ftp.debian.omg:80 (Name or service not known)
Failed to resolve ftp.debian.omg:80 (Name or service not known)
Failed to resolve ftp.debian.omg:80 (Name or service not known)
Failed to resolve ftp.debian.omg:80 (Name or service not known)
Failed to resolve ftp.debian.omg:80 (Name or service not known)
Failed to resolve ftp.debian.omg:80 (Name or service not known)
Failed to resolve ftp.debian.omg:80 (Name or service not known)
Failed to resolve ftp.debian.omg:80 (Name or service not known)
Failed to resolve ftp.debian.omg:80 (Name or service not known)
Failed to resolve ftp.debian.omg:80 (Name or service not known)
Failed to resolve ftp.debian.omg:80 (Name or service not known)
Failed to resolve ftp.debian.omg:80 (Name or service not known)
Failed to resolve ftp.debian.omg:80 (Name or service not known)
Failed to resolve ftp.debian.omg:80 (Name or service not known)
Failed to resolve ftp.debian.omg:80 (Name or service not known)
Failed to resolve ftp.debian.omg:80 (Name or service not known)
Failed to resolve ftp.debian.omg:80 (Name or service not known)
Failed to resolve ftp.debian.omg:80 (Name or service not known)
Failed to resolve ftp.debian.omg:80 (Name or service not known)
[0] Failed to download
But that's not the case for URL schemes.