Custom Query (8073 matches)


Show under each result:

Results (148 - 150 of 8073)

Ticket Resolution Summary Owner Reporter
#934 Remote file times wrong when timezone offset Alexander Schuch superatus

My server is 5 hours behind my local time so I have the timezone offset in FZ preferences set to +5:00 but in FZ 2.2.15 the times are wrong. If I don't offset then FZ shows the correct file times for the server's local time.

But... If I also offset by any number of minutes then the times become correct!

My workaround at the moment is to offset by 5:01.

I'm on Windows XP

Anyone else noticed this?

#936 buggy ftp with explicit encryption Alexander Schuch aisaac0

I have no problems with SFTP using SSH. When I attempt FTP over SSL (or TSL) with explicit encryption in passive mode, I get partial uploads and zero byte uploads. This is a critical failure of FileZilla, which I have hitherto loved.

Tested with the Aug 21 release.

See for examples of others with this problem. It deserves highest priority.

Attached is the debug log:

#944 Latest client hangs while busy. Alexander Schuch twoseven

Just testing out the 2.2.15 client along side the previous version. The setup is two laptops plugged directly into a 100mb/s switch into the server running filezilla server 0.9.10.

When I upload a directory with about 13000 files (700 folders - 390mb) in it the client hangs for about 30 seconds and 'not responding' appears in the title bar. (In case someone is wondering, I was moving a s/w application to another machine)

It then proceeds to list every file in the directory that is to be copied and all sub-directories in the 'remote site' window, which takes approx. another minute, then queues up every file in the process queue taking a further minute (if it takes too long the server times out the connection and it requires the operation to be restarted). It then copies all the files to the server as would be expected. It should not be auto-listing files in the remote window - this is both bad usability and costely in CPU cycles for no reason.

If I delete the directory on the server (via the client remote site window), it then lists out the contents of all the subdirectories in the remote window, again taking ages, then queues them up, then issues a DEL command for every single file - the whole process took 15 mins where all that was needed was a DEL command to be issued on the root directory (the one I selected) and the OS should have done the rest.

When I use the previous version, it does not list out all the files in the remote site window before adding them to the process queue. It also takes less time to do the transfer (perhaps there is a config change or something)

So there are two problems. First, it takes a huge amount of time simply to copy a directory full of files (locking up filezilla), and second why are actions not offloaded to the OS (such as delete the directory, rather than every file individually).

As a comparison, zipping the directory in winzip took 2 mins, Ftp'ng the resulting 190mb file to the server took 1 min and deleting it took half a sec. There is enough information in the windows file system to tell you it was a large transfer and compression is needed - why not use it.

Also, if configurations changes are being made between versions, please list them in a readme as well as bugfixes etc.

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