Page 1 of 1
Specific url protocol
Posted: 2022-09-15 14:12
by theodoretoke
Hi, I know I can access it via the URL of ftp://user@ip:port
But, what if I have multiple FTP programs installed on my machine?
WinSCP has a way to specifically access it via winscp-ftp://user@ip:port
Does anyone know if there's also a way for filezilla? Does Filezilla actually offer a specific protocol for it?
Can't find it anywhere.
Cheers
Re: Specific url protocol
Posted: 2022-09-16 07:03
by boco
No.
Re: Specific url protocol
Posted: 2022-09-19 15:05
by theodoretoke
Do you know if its there a way to work around this?
also, when i use ftp:// and select FileZilla as the program, it encodes the text.
I've a dot ' . ' in my user login credentials and it is replaced with ' . ' in Filezilla.
Re: Specific url protocol
Posted: 2022-09-19 20:14
by boco
Do you know if its there a way to work around this?
Such custom protocols are usually utilized for automation. As FileZilla cannot do automatic transfers anyway, the author didn't find it necessary to bother with that.
also, when i use ftp:// and select FileZilla as the program, it encodes the text.
I've a dot ' . ' in my user login credentials and it is replaced with ' . ' in Filezilla.
I'm pretty sure the encoding is done by the protocol handler and not FileZilla. Protocol handlers in Windows are usually used for browsers and their protocols.
Maybe the author will drop a comment on that issue.
Re: Specific url protocol
Posted: 2022-09-19 22:25
by botg
boco wrote: ↑2022-09-19 20:14
Do you know if its there a way to work around this?
Such custom protocols are usually utilized for automation. As FileZilla cannot do automatic transfers anyway, the author didn't find it necessary to bother with that.
Mostly this.
also, when i use ftp:// and select FileZilla as the program, it encodes the text.
I've a dot ' . ' in my user login credentials and it is replaced with ' . ' in Filezilla.
I'm pretty sure the encoding is done by the protocol handler and not FileZilla. Protocol handlers in Windows are usually used for browsers and their protocols.
Protocol handlers are tricky. Especially on Windows, program argument parsing is a hot mess. There is still much left to be improved for parsing URIs passed from the command-line before registering FZ as URL handler can be considered.