3 ms·
> I understand the technical reasons for that, but it is technically supported by the spec and other clients work with it just fine. I am completely aware of t
by nmgycombinator 2y ago
> I understand the technical reasons for that, but it is technically supported by the spec and other clients work with it just fine.
I am completely aware of that, but I am aware that other clients handle it just fine. The bug actually forced me to use a different client for when I actually needed an FTP client.
- hunter2_ 2y agoI would've guessed that once it's established that the bug is caused by the app injecting the specified username into the USERINFO portion of a URL without the necessary percent-encoding, a workaround (other than using a different client) would be to manually percent-encode the username, i.e., replace the "@" with "%40" ... although this wouldn't work if the app actually did percent-encode an entered "%" despite not encoding an entered "@"!
- nmgycombinator 2y agoFascinating. I'll have to test that out!