Hi, We would like to start using RDP file transfer. We found some issues I would like to discuss:
1. After uploading 64 files in one session (not on the same time), the next uploads fail with an "Invalid stream index" error. I found that the max stream index is 64, and the client holds a pool of stream indices for the uploads. The problem is that it does not mark an index as free when an upload finishes. There is a function that does this - endStream(), but it's not called (the function also sends an "end" instruction which I don't think is relevant in this case). We solved this in our repo by freeing the index when receiving the "loadend" event from the upload ajax call. Is this a known issue? 2. Uploading more than 64 on the same time is not possible due to the max streams limit. We would like to solve it by creating a queue of pending file uploads on the client side. Does this make sense? 3. The following scenario: a. Connect to an end point using Guacamole with drive redirection. b. Assign a drive letter to the redirected drive/folder. c. MSTSC to another machine with drive redirection. d. The Guacamole redirected folder appears on the second machine and uploaded files can be accessed, but when we delete a file (from within the nested RDP session), the file is not deleted. It disappears from file explorer, but appears again upon refresh. It is not deleted from the Guacamole machine. We reproduced the issue on Windows Server 2012 R2 and Windows Server 2016 targets (for the nested RDP session), on Windows Server 2008 R2 it didn't reproduce, delete worked as expected. Any ideas on what can be the reason for this behavior? I know it seems like an esoteric use case, but it's actually our main flow so it's important for us to solve it. Thanks, Gabriel
