Custom Query (8117 matches)
Results (73 - 75 of 8117)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #73 | 1.8 pasv mode freaking out ftp servers | |||
| Description |
When i try to upload with 1.8 in passive mode, i get an error: Status: Starting upload of c:\Program Files\FileZilla\license.txt Command: TYPE A Response: 200 Type set to A. Command: PASV Response: 227 Entering Passive Mode (12,x,2,11,56,16). Command: STOR license.txt Error: Transfer channel can't be opened. Reason: The requested address is not valid in its context. Error: Upload failed On the logs for my ftp server (g6) i see:
allowed.
(17:42:41 - -0.001 KB - 0.000 KBytes/s).
Compared with 1.7b (which works), there was no PASV command issued after STOR. It just goes straight to "data connection." That has to be the reason it's messing up.. right? I tried it real quick to upload to a proftpd server and i got the same error. I hope it's not just me. thnx |
|||
| #74 | Multiple folders download & upload | |||
| Description |
Whe I try to download & upload (with version 1.8) a complex structure of files and directories, Filezilla presents two different problems: a) When downloading more then a folder, it sometimes seems that it just download the first one. It just happens when you put them directly on the queue. If you download a single folder with multiple folders within, it works correctly. b) When uploading, it doesn't create new folders correctly. If you have an empty folder (i.e.: without files) that has some directories, Filezilla tries to create those directories directly, without creating first the folder. The result is that no one of them is created. |
|||
| #75 | replies 150 and 226 on ls come together | |||
| Description |
Just a thought I am not claiming to be an expert on this. The replies to ls 150 and 226 come together on the same server reply. the client has to dig in there to find out that those are actually to responses. I thought it was confusing to the client side it was in my client (my program), nothing I could not handle though. I just though it might be confusing to other clients. I read the RFC959 and it is not clear whether you should send them seperatelly |
|||
