the ftp backend doesn't handle server with limited access correctly
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gvfs |
Fix Released
|
Medium
|
|||
gvfs (Ubuntu) |
Fix Released
|
Low
|
Ubuntu Desktop Bugs |
Bug Description
I have a public FTP server where root directory listing is forbidden and server redirects clients to another working directory basing on its login name implicitly after login. Embedded Nautilus ftp client fails to work with such server because of trying to access "/" instead of current directory. Moreover, when I type correct working directory Nautilus says that it is not found. I checked gFTP and it works just perfect. Windows Explorer also works fine. Please see gFTP output below this message. Hope it helps the community. Do not hesitate to ask any further questions you probably may have, you are welcome.
gFTP output:
TYPE I
200 Type set to I.
PWD
257 "/pHDSN-HAMM" is current directory.
Loading directory listing /pHDSN-HAMM from server (LC_TIME=
PASV
227 Entering Passive Mode (4,78,136,
LIST -aL
125 Data connection already open; Transfer starting.
226 Transfer complete.
Changed in gvfs: | |
status: | Unknown → New |
summary: |
- FTP works incorrectly with custom default folder and forbidden ls - command in / + the ftp backend doesn't handle server with limit access correctly |
summary: |
- the ftp backend doesn't handle server with limit access correctly + the ftp backend doesn't handle server with limited access correctly |
Changed in gvfs: | |
status: | New → Fix Released |
Changed in gvfs: | |
importance: | Unknown → Medium |
Thank you for taking the time to report this bug and helping to make Ubuntu better.
Can you add the output of 'apt-cache policy nautilus' and 'lsb_release -d' ?
Thanks in advance.