Custom Query (8096 matches)
Results (331 - 333 of 8096)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #11936 | duplicate | Client timeout at "performing handshake" when using HTTP proxy | ||
| Description |
Client is unable to connect via HTTP proxy, it gets stuck at "performing handshake". I've been able to do it using the same proxy on earlier FileZilla client versions (WinSCP is working too). Here are the debug messages: Status: Connecting to <<ftp_server>> through HTTP proxy Status: Resolving address of <<proxy_dns>> Status: Connecting to <<proxy_ip:port>>... Status: Connection with proxy established, performing handshake... Error: Connection timed out after 60 seconds of inactivity Error: Could not connect to server Status: Waiting to retry... Status: Connecting to <<ftp_server>> through HTTP proxy Status: Resolving address of <<proxy_dns>> Status: Connecting to <<proxy_ip:port>>... Status: Connection with proxy established, performing handshake... Error: Connection timed out after 60 seconds of inactivity Error: Could not connect to server Status: Disconnected from server Status: Connecting to <<ftp_server>> through HTTP proxy Status: Resolving address of <<proxy_dns>> Status: Connecting to <<proxy_ip:port>>... Status: Connection with proxy established, performing handshake... Error: Connection attempt interrupted by user Status: Disconnected from server Status: Connecting to <<ftp_server>> through HTTP proxy Status: Resolving address of <<proxy_dns>> Status: Connecting to <<proxy_ip:port>>... Status: Connection with proxy established, performing handshake... Error: Connection attempt interrupted by user Status: Disconnected from server Trace: CRealControlSocket::DoClose(66) Trace: CControlSocket::DoClose(66) Trace: CRealControlSocket::DoClose(66) Trace: CControlSocket::DoClose(66) Trace: CControlSocket::DoClose(66) Trace: CFileZillaEnginePrivate::ResetOperation(0) Trace: CControlSocket::SendNextCommand() Trace: CFtpLogonOpData::Send() in state 0 Status: Connecting to <<ftp_server>> through HTTP proxy Status: Resolving address of <<proxy_dns>> Status: Connecting to <<proxy_ip:port>>... Status: Connection with proxy established, performing handshake... Error: Connection timed out after 60 seconds of inactivity Trace: CRealControlSocket::DoClose(2050) Trace: CControlSocket::DoClose(2050) Trace: CFtpControlSocket::ResetOperation(2114) Trace: CControlSocket::ResetOperation(2114) Trace: CFtpLogonOpData::Reset(2114) in state 1 Error: Could not connect to server Trace: CFileZillaEnginePrivate::ResetOperation(2114) Status: Waiting to retry... Trace: CRealControlSocket::DoClose(66) Trace: CControlSocket::DoClose(66) Trace: CControlSocket::DoClose(66) Trace: CControlSocket::SendNextCommand() Trace: CFtpLogonOpData::Send() in state 0 Status: Connecting to <<ftp_server>> through HTTP proxy Status: Resolving address of <<proxy_dns>> Status: Connecting to <<proxy_ip:port>>... Status: Connection with proxy established, performing handshake... Error: Connection timed out after 60 seconds of inactivity Trace: CRealControlSocket::DoClose(2050) Trace: CControlSocket::DoClose(2050) Trace: CFtpControlSocket::ResetOperation(2114) Trace: CControlSocket::ResetOperation(2114) Trace: CFtpLogonOpData::Reset(2114) in state 1 Error: Could not connect to server Trace: CFileZillaEnginePrivate::ResetOperation(2114) |
|||
| #9362 | duplicate | Feature request: extension conversion | ||
| Description |
I edit files in a windows environment. The file extension tells the editor how to behave. The target platform is legacy, where a filename has 1-8 characters only. Request example for copy file from windows to legacy: FILENAM1.CBL -> FILENAM1. Also: FILENAM2.SBL -> FILENAM2. Example for copy file from legacy to windows: PROGNAM1-> PROGNAM1.CBL (only one possibility here). WinFTP Pro has this feature. See also ticket 5400. Thanks. |
|||
| #7800 | fixed | Automatic directory refresh upon transfer completion | ||
| Description |
Currently (FileZilla Client 3.5.1), the target directory doesw not show the actual contents when an upload is completed. The user then has to manually refresh the diretory listing to confirm that the transfered data is there. be a If the directory would automatically refresh, this would not be necessary. Whether the refresh should happen per file transfer or group of transfers could be a user preference, as per file would generate a bit more traffic which might not be necessary for a specific user. FileZilla version used below: FileZilla Client Version: 3.5.1 Build information:
Linked against:
Operating system:
|
|||
