I want to ask, what is the reason for excluding colon from possible characters for a virtual path?
The Error Message: Character '\' is not allowed in the path. Moreover, file and directory names in the path must not include the ':' character and must not terminate with a space or a dot.
I am asking, because our old server software (I try to replace now) supported it before. And the bad thing is, that the changes to the client side are hard to do.
From: https://filezillapro.com/docs/server/ad ... oup-panel/Virtual path format
The format of the virtual path is the same one used by UNIX-like operating systems: files and directories are separated by the slash ‘/’ character and all files and directories belong to a unique root, whose name is exactly ‘/’. Virtual paths are normalized by resolving all . and ..
directories and removing any trailing ‘/’ character.
And on the docs - the colon is not forbidden/explained.
This is the old path, what was previously a mounted network drive.
In my opinion, the limitations for colons on a windows client, is only a ftp client "problem" which should be handled (translated) on that place - not a limitation for the ftp server. Or is there any RFC which forbids colons in paths?
Or I am doing something wrong? Or is there a "hack" to overcome the limitation by using any escape characters or stuff like : or something?