Opened 14 years ago

Last modified 6 years ago

#1094 closed Bug report

0 Byte Uploads -> timeout!

Reported by: maconey Owned by:
Priority: normal Component: FileZilla Client
Keywords: Cc: maconey, Tim Kosse
Component version: Operating system type:
Operating system version:

Description

Hi,

i'm uploading the newest version of wordpress with
filezilla, and there are some 0 bytes files.

This is the log of a 0 byte file:

[...]
Status: Starte Upload von
T:\Temp\wordpress\wp-includes\js\tinymce\plugins\autosave\langs\sv.js
Befehl: TYPE A
Antwort: 200 Type set to A
Befehl: PASV
Antwort: 227 Entering Passive Mode
(XXX,XXX,XXX,XXX,XXX,XXX).
Befehl: STOR sv.js
Antwort: 150 Opening ASCII mode data connection for sv.js
Fehler: Timeout entdeckt!
Fehler: Upload fehlgeschlagen
[...]

This happens with every 0 byte file.

Attachments (1)

FlashFXP.log (2.9 KB) - added by maconey 14 years ago.
FlashFXP 0 bytes upload log.

Download all attachments as: .zip

Change History (7)

comment:1 Changed 14 years ago by Tim Kosse

I cannot reproduce this, does it happen with other clients
as well?

comment:2 Changed 14 years ago by maconey

i've tested it with gftp, and there is no timeout.

gftp log:

PASV
227 Entering Passive Mode (xxx,xxx,xxx,xxx,xxx,xxx).
STOR /0bytes
150 Opening BINARY mode data connection for /0bytes
226 Transfer complete.
/tmp/0bytes erfolgreich mit 0,00 KB/s übertragen
SITE CHMOD 644 /0bytes
200 SITE CHMOD command successful
Lade Verzeichnisliste / von der Gegenstelle
(LC_TIME=de_DE.UTF-8)
PASV
227 Entering Passive Mode (xxx,xxx,xxx,xxx,xxx,xxx).
LIST -L
150 Opening ASCII mode data connection for file list
226 Transfer complete.

and again, filezilla 2.2.24a log:

Status: Starte Upload von c:\0bytes
Befehl: TYPE I
Antwort: 200 Type set to I
Befehl: PASV
Antwort: 227 Entering Passive Mode (xxx,xxx,xxx,xxx,xxx,xxx).
Befehl: STOR 0bytes
Antwort: 150 Opening BINARY mode data connection for 0bytes
Fehler: Timeout entdeckt!
Fehler: Upload fehlgeschlagen

doesn't filezilla close the data connection? sorry, i don't
know what a type of ftp server this is. greeting is

Antwort: 220 wpXXX.webpack.hosteurope.de FTP server ready
Befehl: AUTH TLS
Antwort: 234 AUTH TLS successful
Status: SSL-Verbindung hergestellt. Warten auf
Willkommens-Meldung...
Befehl: USER ftpXXXXXXXX-XXXX
Antwort: 331 Password required for ftpXXXXXXXX-XXXX.
Befehl: PASS XXXXXXXXXXXXX
Antwort: 230 User ftp1006543-matze logged in.
Befehl: SYST
Antwort: 215 UNIX Type: L8
Befehl: FEAT
Antwort: 211-Features:
Antwort: MDTM
Antwort: REST STREAM
Antwort: SIZE
Antwort: AUTH TLS
Antwort: PBSZ
Antwort: PROT
Antwort: 211 End
Befehl: PBSZ 0
Antwort: 200 PBSZ 0 successful
Befehl: PROT P
Antwort: 200 Protection set to Private

comment:3 Changed 14 years ago by Tim Kosse

Isn't gftp a linux client? Please try another client under
windows.

comment:4 Changed 14 years ago by maconey

gftp is linux. i've tried it with FlashFXP 3.3.8 (build 1133
)RC2 and it upload worked without timeout. (log see attached
file)

I've also installed a clean Filezilla with default config,
createt one account and changed no settings, the same
problem, timeout.

The Connection-type for this Server is FTP over TLS.
I've tested it on other severs (connection type ftp). There
was no timeout with Filezilla.

Changed 14 years ago by maconey

Attachment: FlashFXP.log added

FlashFXP 0 bytes upload log.

comment:5 Changed 14 years ago by Tim Kosse

Why didn't you say you're using SSL in your original bug
report? Such information is very important.

Now FlashFXP seems to use the PROT C command to upload the
file, thus bypassing SSL. What happens if you use a
different client that uploads in SSL mode without using PROT C?

Also, which server are you using?

Would it be possible to get a temporary guest account on
your server where I can upload empty files?

comment:6 Changed 14 years ago by sf-robot

This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).

Note: See TracTickets for help on using tickets.