Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Connecting to wrong port doesn't throw exception or timeout #274

Closed
AlKau opened this issue Feb 16, 2018 · 3 comments
Closed

Connecting to wrong port doesn't throw exception or timeout #274

AlKau opened this issue Feb 16, 2018 · 3 comments

Comments

@AlKau
Copy link

AlKau commented Feb 16, 2018

FTP OS: (ftp://test.rebex.net)

FTP Server: (ftp://test.rebex.net)

Computer OS: Win10

App: UWP

Fluent FtpClient has default settings.
It can connect to ftp://test.rebex.net:21 or ftp://test.rebex.net:990 (use Task FtpClient.ConnectAsync()).
When type wrong port like 22, 143 (I think the port should be open but not ftp) the task never ends.

p.s. I can't write logs, because I don't know how to include it in UWP

@robinrodricks
Copy link
Owner

You could save logs to a textfile. There is an option for that even in the UWP version.

@AlKau
Copy link
Author

AlKau commented Mar 6, 2018

nuget FluentFTP v19.1.2
I added FtpTrace.LogToFile = "log_file.txt";
and got exception System.UnauthorizedAccessException: 'Access to the path 'C:\Development\FtpTest\bin\x64\Debug\AppX\log_file.txt' is denied.' on line await _client.ConnectAsync();

UWP can access to file system using StorageFile class.
Can you add custom log?
FtpTrace.CustomLog = (log) => { Debug.WriteLine(log); }

@robinrodricks
Copy link
Owner

Connecting reworked in v40. Please add a new issue if this still occurs. Closing for now.

@robinrodricks robinrodricks closed this as not planned Won't fix, can't repro, duplicate, stale Sep 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants