Opened 4 years ago

Closed 4 years ago

#11997 closed Bug report (invalid)

Pipelining readdir requests

Reported by: Razvan Dumitru Owned by:
Priority: normal Component: FileZilla Client
Keywords: pipelining Cc:
Component version: 3.44.2 Operating system type: Windows
Operating system version: Microsoft Windows [Version 10.0.17763.678]


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.

Change History (1)

comment:1 by Razvan Dumitru, 4 years ago

Resolution: invalid
Status: newclosed

As I was already suspecting, the issue was on my server.

Note: See TracTickets for help on using tickets.