Add support for escaping of certain special characters

(Running 4.2.4)

Some FTPds and/or filesystems take characters such as { and } as special characters. As a result those symbols can be ignored.

Examples:

[R] CWD Go Here {I am insane}
[R] 550 Go Here I am insane: No such file or directory.

A manual CWD with \{ and \} the FTPd can visit said directories

CWD Go Here \{I am insane\} will work without an issue.

Can you give me an example of a FTP server that does this?

In my opinion this would be a bug in the FTP server path parser, surely this can't be the intended behavior because escaping {} isn't required on any major FTP server.

I suppose we could check the error reply and if the path stripped out the {} then try again with the {} escaped, apart from trying again on failure I don't see a good way to work around this problem.

The ideal solution would be to correct the problem in the ftp server software.

I'm uncertain of the software. However here is the connect line, perhaps you know the version off the top of your head. (It's running on FreeBSD)

[R] 220 host.name.replaced FTP server (Version 6.00LS+TLS) ready.
[R] USER username
[R] 331 Password required for username.
[R] PASS (hidden)
[R] 230 User username logged in, access restrictions apply.
[R] SYST
[R] 215 UNIX Type: L8 Version: BSD-199506
[R] FEAT
[R] 211- Extensions supported:
[R] AUTH TLS
[R] PBSZ
[R] PROT
[R] SIZE
[R] MDTM
[R] REST STREAM
[R] 211 End.

Is this still an issue? If so I'd like to see if we can figure out exactly what FTP server software this is.