Ticket #149 (reopened enhancement)

Opened 5 years ago

Last modified 5 years ago

normal FTP server

Reported by: alexander.meyer@leserauskunft.de Owned by: alamaison
Priority: major (affects peripheral workflow) Milestone: 2.0 Extra features
Component: backend Version:
Keywords: FTP Cc:

Description

Hi,
your tool looks great, because it has its only "environment" and doesn't waste valuable drive letters.
But why you don't support normal FTP (not SFTP) connections? I know there are already some tools, but people just want to have a single place where to look for.
Best regards,
Alexander Meyer.

Change History

comment:1 in reply to: ↑ description ; follow-up: ↓ 2 Changed 5 years ago by alamaison

  • Status changed from new to closed
  • Resolution set to wontfix

Replying to alexander.meyer@…:

But why you don't support normal FTP (not SFTP) connections? I know there are already some tools, but people just want to have a single place where to look for.

Normal FTP support is already built into Windows Explorer (since Windows 2000). Swish was created to extend this support to SFTP. Try putting a ftp:// URL into a Windows Explorer address bar and see what happens.

comment:2 in reply to: ↑ 1 ; follow-up: ↓ 3 Changed 5 years ago by caiadmin

Replying to alamaison:

Replying to alexander.meyer@…:

But why you don't support normal FTP (not SFTP) connections? I know there are already some tools, but people just want to have a single place where to look for.

Normal FTP support is already built into Windows Explorer (since Windows 2000). Swish was created to extend this support to SFTP. Try putting a ftp:// URL into a Windows Explorer address bar and see what happens.

The problem with the built-in Windows Explorer based FTP is that it does not handle multiple logins to the same FTP server. For instance, let's say you have an ftp server located at  ftp://ftp.server.com. On that server, you have separate usernames (user1 and user2) with separate passwords (each username represents a separate FTP site on the server). This might seem strange, but it is the way many Linux-based FTP servers work. If you login as user1 using the Windows Explorer method, you will be unable to login to the user2 site (Windows Explorer sees the same URL, and automatically uses the same login - instead of accessing the user2 site, a copy of the user1 site is presented again). In order to access the user2 site, you must logoff of Windows, log back in again, and open the user2 site first.

It would be great to have an open source tool such as Swish to get around this limitation of Windows, rather than having to use WebDrive? or the old Novell NetDrive? software.

comment:3 in reply to: ↑ 2 Changed 5 years ago by alamaison

  • Status changed from closed to reopened
  • Resolution wontfix deleted
  • Component changed from authentication to backend
  • Milestone changed from 0.90 Beta 1 to 2.0 Extra features

Replying to caiadmin:

Replying to alamaison:

Replying to alexander.meyer@…:

But why you don't support normal FTP (not SFTP) connections? I know there are already some tools, but people just want to have a single place where to look for.

Normal FTP support is already built into Windows Explorer (since Windows 2000). Swish was created to extend this support to SFTP. Try putting a ftp:// URL into a Windows Explorer address bar and see what happens.

The problem with the built-in Windows Explorer based FTP is that it does not handle multiple logins to the same FTP server.

I've reopened the ticket as I'm happy to include FTP in Swish if we can make a better job of it than the built-in client does. But it's won't happen any time soon unless someone steps up to write the code.

Note: See TracTickets for help on using tickets.