Custom Query (8167 matches)
Results (235 - 237 of 8167)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#1385 | An unhandled win32 exception occurred in filezilla.exe | |||
Description |
I connected an FTPS server(port 990), and then closed filezilla. After filezilla UI hided, an dialog shown: "An unhandled win32 exception occurred in filezilla.exe [3480]." with title "Visual Studio Just-In-Time Debugger". My OS is Windows XP with SP2. I installed Visual Studio 2005. with FTP, all is OK. with FTPS, the exception is occurred. |
|||
#1395 | missing file time on list command | |||
Description |
After changing the modification time using the MFMT command the LIST command just returns only the date and not the time. Example: LIST response before MFMT
LIST response after MFMT
(should be Nov 20 2005 01:00) Looking at the server side shows that the modification time was set to the correct value. |
|||
#1396 | Failed to upload file | |||
Description |
There is a ftp proxy between filezilla and ftp server. The ftp proxy caches data and do virus scanning before transmit it. Use filezilla to upload a big file, filezilla failed: 状æ€: è¿æ¥åˆ° 192.168.10.43:21... 状æ€: è¿æ¥å»ºç«‹ï¼Œç‰å¾…欢è¿æ¶ˆæ¯... è¿”å›: 220 Serv-U FTP Server v6.4 for WinSock ready... 命令: USER test è¿”å›: 331 User name okay, need password. 命令: PASS è¿”å›: 230 User logged in, proceed. 状æ€: å·²è¿æ¥ 状æ€: å¼€å§‹ä¸Šä¼ C:\ftp test\A1000-100.00.0.56.acv 命令: CWD /2009/ è¿”å›: 250 Directory changed to /2009 命令: PWD è¿”å›: 257 "/2009" is current directory. 命令: TYPE I è¿”å›: 200 Type set to I. 命令: PASV è¿”å›: 227 Entering Passive Mode (192,168,10,43,18,200) 命令: STOR A1000-100.00.0.56.acv è¿”å›: 150 Opening BINARY mode data connection for A1000-100.00.0.56.acv. è¿”å›: 226-transferring data... è¿”å›: 226-transferring data... è¿”å›: 226-transferring data... 错误: å·²ä»æœåŠ¡å™¨æ–å¼€ The ftp proxy sending "226-transferring data..." to ftp client while doing virus scanning to avoid ftp timeout. Without these resonse, cuteftp and leadftp will timeout, and can work well with these response. But filezilla failed. Disable filezilla timeout, filezilla failed, too. It seems filezilla can't recognize these response correctly. |