[Improvement] Validate SMB2/SMB3 port in VFS URL

[maneeshaheshan]

Hi Team,

When using smb2/smb3 with MI, if we provided the port, it will not be considered even if we passed it as as follows,

smb2://[username]:[password]@[hostname]:[port]/[absolute-path

In the above URI format the [:port] was included as part of the URL. But when the we are trying to use any ports as part of the URL, it seems that to ignored by the MI server.

Also in an ideal scenario, if the we use an invalid port, such as "1234," within the URI, the VFS transport in WSO2 MI 4.2.0 should not function and should generate an error (typically "Invalid URI"). However, MI 4.2.0 does not seem to strictly consider the port validity as long as the remaining components of the URI are correct.

So it would be a good improvement to have the port considered in a future release.