Custom Query (7823 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (52 - 54 of 7823)

Ticket Resolution Summary Owner Reporter
#7804 fixed whitespace in filename cause download failure Chun-Hao Wu
Description

I happen to have a file named ' 01.xxx.mp3' (xxx was Taiwanese). The whitespace prefixing the file name causes downloading errors. The filezilla server log shows the process.

(000005)2011/10/29 下午 23:56:44 - user (211.76.77.44)> 227 Entering Passive Mode (140,113,205,141,8,75) (000005)2011/10/29 下午 23:56:44 - user (211.76.77.44)> RETR 01.xxx.mp3 (000005)2011/10/29 下午 23:56:44 - user (211.76.77.44)> 550 File not found

Yes, the filezilla client correctly requested the filename as 'RETR 01.xxx.mp3', which has two whitespaces after RETR. It's just the server cannot find it.

The issue can be worked around by deleting the prefixing whitespace. It's weird that when I tried to rename ' 01.xxx.mp3' to '01.xxx.mp3', windows 7 told me a file with that name already exists. I copied that file to the same directory, getting both '01.xxx.mp3' and ' 01.xxx.mp3'. Then, I deleted ' 01.xxx.mp3' and this time I can download '01.xxx.mp3' as usual.

So I'm unsure if this issue belongs to filezilla server or windows 7 or the FTP protocol.

Perhaps the problem is that all whitespaces between RETR and the filename are ignored by filezilla server?

#8249 outdated when downloading a directory tree, a random part of it may not be downloaded matteo sisti sette
Description

I right-clicked on a directory (that contained a lot of subdirectories with thousands of files) on the server and selected "download".

During the download process I lost connection a few times and sometimes had to restart filezilla (because of another bug, that sometimes you can't resume processing a queue until you restart filezilla), but then I always resumed; that shouldn't be a problem at all. I never, ever deleted anything from the queue nor did I ever receive any error prompt to which I could have given the wrong answer.

After hours of downloading, the queue was finally empty and FileZilla was apparently done downloading. Then I found out that more than half of the directory tree simply HADN'T BEEN DOWNLOADED.

I don't know whether the missing directories have never got into the queue (I'm ALMOST sure this was the case) or if they did and then they failed to download, but in both cases SILENTLY failing to download is a disaster.

If a queue becomes empty and you haven't explicitely deleted anything from it, you must be 100% sure that everything in it has been downloaded. And if you download a folder, you must have 100% guarantee that all its contents get added to the queue.

I SUSPECT that the queue is built (i.e. the directory tree scanned) while the download is ongoing, so in case of huge directories, if the download is interrupted and resumed, maybe the scanning of the directory is not resumed properly. If that is the case, than that is the bug. Either the whole scanning of directories and queuing of files should be done prior to starting to download, OR actions should be taken to ensure that in case of interruptions the scanning is resumed reliably.

Assuming that downloading a directory tree is always done without the slightest network error or without restarting FileZilla from the beginning to the end in one chunk, is a ridiculous assumption.

#4481 rejected when connected no directory listing is possible SamS
Description

filezilla client: 3.2.4.1

Status: Benutze Proxy cache1.xxxxxxxxx Status: Auflösen der IP-Adresse für cache1.xxxxxxxxx Status: Verbinde mit xxxxxxxxxxxxxxx:21... Status: Verbindung hergestellt, warte auf Willkommensnachricht... Antwort: 220 XXX FTP Proxy Service Befehl: USER swschis@xxxxxxxxxxxxxxx Antwort: 331 Password required for swschis Befehl: PASS * Antwort: 230 Logged on Befehl: SYST Antwort: 215 UNIX emulated by FileZilla Befehl: FEAT Antwort: 211-Features: Antwort: MDTM Antwort: REST STREAM Antwort: SIZE Antwort: MODE Z Antwort: MLST type*;size*;modify*; Antwort: MLSD Antwort: UTF8 Antwort: CLNT Antwort: MFMT Antwort: 211 End Status: Verbunden Status: Empfange Verzeichnisinhalt... Befehl: PWD Antwort: 257 "/" is current directory. Befehl: TYPE I Antwort: 200 Command okay. Befehl: PASV Antwort: 227 Entering Passive Mode (10,126,101,11,43,215) Befehl: MLSD Antwort: 503 Bad sequence of commands. Fehler: Verzeichnisinhalt konnte nicht empfangen werden Status: Empfange Verzeichnisinhalt... Befehl: CDUP Antwort: 250 CDUP command successful. Befehl: PWD Antwort: 257 "/" is current directory. Befehl: PASV Antwort: 227 Entering Passive Mode (10,126,101,11,140,0) Befehl: MLSD Antwort: 503 Bad sequence of commands. Fehler: Verzeichnisinhalt konnte nicht empfangen werden

downgraded to version 3.2.1 it reads like this and is working proberly:

Status: Benutze Proxy cache1.xxxxxxxxx Status: Auflösen der IP-Adresse für cache1.xxxxxxx Status: Verbinde mit xxxxxxxxxxxxx:21... Status: Verbindung hergestellt, warte auf Willkommensnachricht... Antwort: 220 XXX FTP Proxy Service Befehl: USER swschis@xxxxxxxxxxxxxxxxxx Antwort: 331 Password required for swschis Befehl: PASS * Antwort: 230 Logged on Befehl: SYST Antwort: 215 UNIX emulated by FileZilla Befehl: FEAT Antwort: 211-Features: Antwort: MDTM Antwort: REST STREAM Antwort: SIZE Antwort: MODE Z Antwort: MLST type*;size*;modify*; Antwort: MLSD Antwort: UTF8 Antwort: CLNT Antwort: MFMT Antwort: 211 End Status: Verbunden Status: Empfange Verzeichnisinhalt... Befehl: PWD Antwort: 257 "/" is current directory. Befehl: TYPE I Antwort: 200 Command okay. Befehl: PASV Antwort: 227 Entering Passive Mode (10,126,101,11,214,220) Befehl: LIST Antwort: 150 File status okay; about to open data connection. Auflistung: -rw-r--r-- 1 ftp ftp 1222656 Feb 18 2009 7z465-x64.msi Auflistung: -rwxr-xr-x 1 ftp ftp 939956 Feb 18 2009 7z465.exe Auflistung: drwxr-xr-x 1 ftp ftp 0 Apr 14 16:30 BO-XI-Transfer Auflistung: drwxr-xr-x 1 ftp ftp 0 Dec 18 2008 EasyTransferDaemon Auflistung: drwxr-xr-x 1 ftp ftp 0 Feb 20 2009 easy_data Auflistung: drwxr-xr-x 1 ftp ftp 0 Mar 27 2009 Easy_Neue_Version Auflistung: drwxr-xr-x 1 ftp ftp 0 May 05 07:12 EXPORT Auflistung: drwxr-xr-x 1 ftp ftp 0 Mar 03 2009 htdocs Auflistung: drwxr-xr-x 1 ftp ftp 0 May 04 07:57 Parameter_PeriodicJobs Auflistung: drwxr-xr-x 1 ftp ftp 0 Jan 23 2009 PDF-Datenrettung Auflistung: -rw-r--r-- 1 ftp ftp 18405197 Dec 18 2008 preprod.7z Auflistung: drwxr-xr-x 1 ftp ftp 0 Dec 18 2008 preprod_Aus_xxxxxxxx Auflistung: -rw-r--r-- 1 ftp ftp 3015 Apr 01 10:46 xxxxxxxxxxxxxxxxxxxxxxx2009-04-01_10-46-35.238.xml Auflistung: -rwxr-xr-x 1 ftp ftp 12337752 Dec 18 2008 rktools.exe Auflistung: drwxr-xr-x 1 ftp ftp 0 Mar 03 2009 RMS_Standalone_Job_1 Auflistung: -rwxr-xr-x 1 ftp ftp 79872 Apr 18 2003 robocopy.exe Auflistung: -rw-r--r-- 1 ftp ftp 75 Dec 18 2008 RoboCopyPDF_Rettung.cmd Auflistung: drwxr-xr-x 1 ftp ftp 0 Apr 01 11:11 transfer Antwort: 226 Transfer complete, closing data connection. Status: Berechne Zeitzonenabweichung des Servers... Befehl: MDTM xxxxxxxxxxxxxxxxxxxxx2009-04-01_10-46-35.238.xml Antwort: 213 20090401084635 Status: Zeitzonenabweichungen: Server: 7200 Sekunden. Lokal: 7200 Sekunden. Differenz: 0 Sekunden. Status: Anzeigen des Verzeichnisinhalts abgeschlossen

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.