Custom Query (8143 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (172 - 174 of 8143)

Ticket Resolution Summary Owner Reporter
#1001 *ULTRA* minor bug Alexander Schuch ahva410
Description

I noticed when I was FTPing files between two computers on my 100mbit LAN that on the server side of things, its showing the current throughput, but, when it reaches to over 1000, it places the comma in the wrong spot. Instead of 1,000, its showing 10,00kb/s. Quick fix, but not worthy of a new release. ;)

#1002 After using sftp:// a plain address does no ftp connection Alexander Schuch claudionieder
Description

A filezilla user asked me to report to you this bug:

He sees an inconsistency on how the address field is handled. When you type in just a host name, filezilla makes an FTP connection.

But in this sequence of events things are different (note: you need to use for ftp.example.com a host which supports FTP but no SFTP):

  1. Start up FileZilla version 2.2.17a
  2. Fill in an Address like sftp://ftp.example.com
  3. Discover, that ftp.example.com does not support

SFTP, so Click on the STOP icon in the Toolbar.

  1. Remove the sftp:// prefix in front and try to

connect to ftp.example.com instead. It still will not connect.

This happens, because filezilla still tries to establish connections to port 22. You would need to extend the address to ftp://ftp.example.com to get a connection.

This is irritating to unexperienced users, because for them it looks like the situation in step 4 is the same as if they had gone through this sequence of events:

  1. Start up FileZilla version 2.2.17a
  2. Fill in an Address like ftp.example.com
  3. An FTP connection is set up.
#1004 Resume bug still in 2.2.18 Alexander Schuch karmikal
Description

Filezilla resumes while OVERWRITE is selected In my case the file on the host is appended to the size of the file on the client. If the size on the host is smaller or same, the file is left untouched. (The REST command starts at the host file size) This often and apparently randomly causes files to be uploaded incorrectly.

Note the APPE appear all of a sudden in the commands log below


Status: Connected Status: Starting upload of d:\post_production\maps\0000000451.gif Command: PWD Response: 250 "/Zoom1Images/maps/": is current directory. Command: PWD Response: 257 "/" is current directory. Command: CWD /Zoom1Images/maps/ Response: 257 "/Zoom1Images/maps/" is current directory. Command: TYPE A Response: 250 "/Zoom1Images/maps/": is current directory. Command: PWD Response: 200 Type set to A. Command: PASV Response: 257 "/Zoom1Images/maps/" is current directory. Command: TYPE A Response: 227 Entering Passive Mode (192,168,111,7,107,192) Command: LIST Response: 200 Type set to A. Command: PASV Command: TYPE A Response: 150 Opening ASCII mode data connection for /bin/ls (31547 bytes). Response: 227 Entering Passive Mode (192,168,111,7,74,91) Command: LIST Response: 200 Type set to A. Response: 226 Transfer complete. 31547 bytes in 0.17 sec. (179.114 Kb/s) Response: 150 Opening ASCII mode data connection for /bin/ls (31547 bytes). Command: TYPE I Response: 200 Type set to I. Command: PASV Response: 227 Entering Passive Mode (192,168,111,7,76,88) Command: APPE 0000000292.gif Response: 125 Ready to receive "0000000292.gif" (restart at 47441 bytes). Mode STREAM Type BINARY. Response: 226 Transfer complete. 31547 bytes in 0.00 sec. (30807.617 Kb/s) Command: TYPE I Response: 200 Type set to I. Command: PASV Response: 227 Entering Passive Mode (192,168,111,7,78,37) Command: STOR 0000000451.gif Response: 125 Ready to receive "0000000451.gif" . Mode STREAM Type BINARY. Response: 226 Transfer complete. 79 bytes in 0.03 sec. (2.489 Kb/s) Status: Upload successful

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