Custom Query (7896 matches)
Results (19 - 21 of 7896)
|#11997||invalid||Pipelining readdir requests|
Something seems strange with the way the client is handling responses to readdir requests.
I just finished support to handle this kind of client behavior in a SFTP server I am working on but FileZilla does not seem to handle the replies correctly, complaining about wrong request id.
Interaction log looks like this:
(FileZilla) ID:256 SSH_FXP_OPENDIR. (Server) ID:256 SSH_FXP_HANDLE. (FileZilla) ID:256 SSH_FXP_READDIR. (FileZilla) ID:257 SSH_FXP_READDIR. (FileZilla) ID:258 SSH_FXP_READDIR. (FileZilla) ID:259 SSH_FXP_READDIR. (Server) ID:256 SSH_FXP_NAME count:5. (FileZilla) ID:256 SSH_FXP_READDIR. (Server) ID:257 SSH_FXP_STATUS errnum:1. (Server) ID:258 SSH_FXP_STATUS errnum:1. (Server) ID:259 SSH_FXP_STATUS errnum:1. (Server) ID:256 SSH_FXP_STATUS errnum:1.
Maybe I'm missing something obvious here but looking at the order of sequence ids send by the client and the order in which the server sends its responses, the listing should end successfully.
The server is closed source so I'm unable to share code or make it available for testing.
Can save save/transver all files from your client to the server except .taccess files never have this issues before and using you from years.... is your quality and support will change in microsoft?
|#1843||Per-site firewall (SOCKS) settings|
A single proxy/SOCKS setting is fine for if I am using it to connect to servers on the Internet, but not so for use inside complex network environments.
Per site proxy settings are essential for use in any larger corporation, or supporting multi-client environments. For example, I work for an outsourcing company and to connect to client A, I need to use SOCKS server a, and to connect to client B, I need to use SOCKS server b, and so on, as we have a SOCKS server that acts as a gateway to every client network. In order to use FileZilla for this, every time I connect to a different site I have to go to the settings and manually change the firewall options.
Note: This would be consistent with how products such as PuTTY work. Currently I connect to the same servers via SSH using PuTTY, and for each connection I define in PuTTY, I can set the SOCKS server (and SOCKS userid/password).
In summary - please consider adding this, as the client is great other than this issue. (I read that the site manager was getting a make-over at some stage so maybe this could be part of that?)