There is a bug in the protocol parsing code that makes it incorrectly recognize protocols in URIs that actually don't have any protocol specified, but start with "ftp", "sftp" etc. For example, "ftp.company.com" will be handled incorrectly.
The fix is trivial: a protocol always ends with a semicolon (ftp:, sftp: etc).
There is a bug in the protocol parsing code that makes it incorrectly recognize protocols in URIs that actually don't have any protocol specified, but start with "ftp", "sftp" etc. For example, "ftp.company.com" will be handled incorrectly.
The fix is trivial: a protocol always ends with a semicolon (
ftp:
,sftp:
etc).