GNOME Bugzilla – Bug 541737
"Invalid Reply" while trying to mount Libra FTP Server
Last modified: 2009-01-13 16:08:50 UTC
Please describe the problem: FTP does not work in Nautilus, at least with some sites. I've created an empty test FTP site for the bug report testing purposes. ftp.narod.ru login:ftpset password:123456 Nautilus cannot connect this site, while any file browser (Mozilla, Epiphany, IE) as well as FTP client (Total Commander, command-line ftp) do connect this site without any problem. Steps to reproduce: Actual results: Expected results: Does this happen every time? Other information:
Thanks for reporting. Can you tell us the server software that server is using, and whether it works when connecting using gvfs-mount?
This is a public server. I do not know the software. You can test gvfs-mount yoiurself. This server accessible from any point on Earth.
By the way. I use Ubuntu 8.04 and there is no gvfs-mount. There is no such package even in the repository.
In Ubuntu you must install the gvfs-bin package first. Moving to GVFS as the problem seems to be coming from there (I get "invalid reply"). For testing, the server's source is available here: http://libraftp.narod.ru/
The response of the server is " 220 first-ftp.narod.ru (Libra FTP daemon 0.17 20080704)" while it should be "220 first-ftp.narod.ru (Libra FTP daemon 0.17 20080704)" . So we have two issues: a) libraftp should not send a space at the beginning of the 220 response b) gvfs can not deal with spaces at the beginning of responses
(In reply to comment #5) > The response of the server is > " 220 first-ftp.narod.ru (Libra FTP daemon 0.17 20080704)" That's not how it looks to me. If I telnet to port 21 on ftp.narod.ru I get a perfectly looking greeting message which starts with 220.... If I look at the gvfsd debug output I get this: <-- 220 first-ftp.narod.ru (Libra FTP daemon 0.17<-- 20080704) The problem seems to be that the greeting string contains a end-of-string ('\0') character, making it two replies as far as gvfs is concerned. I guess we should make sure to read up until the newline instead of "newline or string-end", but is it worth working around all weird ftp server behaviour in gvfs? I can't reproduce the problem with Libra FTP Daemon version 1.3.6 from http://libraftp.narod.ru/ and since ftp.narod.ru says it's version 0.17 which is quite a bit lower, maybe it's just time for them to upgrade to resolve this?
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 525283 ***