Over a 7-day period, only .1-.2% of users end up navigating to any FTP URL (with slightly higher numbers amongst Linux desktop users). This has been fairly stable over the last year, so it doesn't look there are trends for FTP to disappear altogether.

FTP サイトで、ファイルのアップロード、ファイルの削除、フォルダー構造の変更を行うには、Windows エクスプローラーでサイトを開く必要があります。単に FTP サイトを開いてそこからファイルをダウンロードする場合は、Internet Explorer を使用できます。Windows エクスプローラーで自動的にサイトが開くように FTP へのショートカットを作成するには、以下の手順を実行します。

11/10/10

Current row

esotericmind said:

I have worked out why this stopped working and found a resolution for my specific setup. The issue seems to be that the latest version of Chrome is using "Extended Passive Mode" (EPSV) for the FTP transfer mode. Internet Explorer still uses standard passive mode (PSV).

My FTP server is sat behind a firewall and only had port 21 forwarded to the FTP server. This works fine for PSV mode. However, EPSV mode uses port 21 for the control connection and a random port number for the data transfer. The port number range that Filezilla was using was somewhere between 2400 and 2600. So i added another port forward (in additon to port 21) to map port numbers 2000-3000 to the FTP server and it all works with Chrome again now. I think Filezilla allows you to specify some custom port numbers to make it easier to handle this situation with NAT and port forwarding.

Hope this helps the rest of you guys out!

+1

FTPにはパッシブモードと言うのがあってIEもFireFoxもパッシブモードを使用していた。が、その中でもEPSVコマンドがFireFoxには無かった。

Some browsers like Firefox use Passive (PASV) mode, AFAIK Opera even uses Extended Passive (EPSV). IE has a setting for Active (PORT) vs. Passive mode, with old versions defaulting to Active and recent to Passive. A real mess.

Well, what DO they use? They use ange-ftp addresses

for FTP (like info.cern.ch:/pub/www/doc/*.ps),