Post a reply

Before posting, please read how to report bug or request support effectively.

Bug reports without an attached log file are usually useless.

Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)


Topic review


Re: Session hangs and eventually closes and have to reconnect if there are trailing spaces in path

Do I understand right, that you are trying to open an invalid path (with additional spaces) and you expect WinSCP to fix the path for you? What what if you really wanted to open a path with spaces in its name?


Anyway, WinSCP should not hang and disconnect.

Please attach a full session log file showing the problem (using the latest version of WinSCP).

To generate the session log file, enable logging, log in to your server and do the operation and only the operation that causes the error. Submit the log with your post as an attachment. Note that passwords and passphrases not stored in the log. You may want to remove other data you consider sensitive though, such as host names, IP addresses, account names or file names (unless they are relevant to the problem). If you do not want to post the log publicly, you can mark the attachment as private.

Session hangs and eventually closes and have to reconnect if there are trailing spaces in path


Build verison I am using : Version 5.9.2, Build 6958.
However this has been there for a long time, but I am only reporting it now as i was expecting it to have been already reported and "will be fixed" in future releases.

Steps to reproduce:
1) Establish a remote SCP to any linux server.(i only have linux servers, so have to mention this)
2) Try to do a change directory on the session to which we have opened.
the directory we are trying a cd to should have prefixed /trailing spaces in the path (normally possible since we copy paste paths which are huge)
Example : correct path "/home/spn221" , path given "/home/spn221 " or " /home/spn221"
In both these cases , the session hangs and have to eventually reconnect.
As it is easy to trim spaces which are before or after a string, i feel this is a bug that can be fixed easily as the side effects are of serious nature or an error be thrown back that the dir is invalid.