Skip to content

New FtpSslSessionReuseException #1224

Closed

Description

@robinrodricks

@FanDjango what is your thought on absorbing errors like this and instead throwing a special exception with the exact advise you give out on the forums?

SSL connection failed; session reuse required -> FtpSslSessionReuseException which then has the message "You need to 1) upgrade your FTP server to the latest or 2) disable SSL session reuse in your FTP server or 3) use FluentFTP.GnuTLS which supports SSL session reuse"

It should reduce the workload of constantly answering the same damn thing when it comes up as a bug ticket.

What say? Is it possible? Is it viable?

Activity

  1. changed the title [-]SSL connection failed; session reuse required[/-] [+]New FtpSslSessionReuseException[/+] on Mar 1, 2023
  2. FanDjango commented on Mar 1, 2023

    @FanDjango
    Collaborator

    excellent idea.

    I sometimes prefer one or two lines of "ERROR" messages prior to a normal exception.

    Also: Not every failure to authenticate the 2nd, 3rd, 4th, etc. connection (i.e. the data connection) is due to session resume problems, although we currently seem to be getting only these errors.

    But by all means…

  3. FanDjango commented on Mar 1, 2023

    @FanDjango
    Collaborator
    if (connection == data_connection)...
     {message with advice
     throw (possible resume failure exception)
    }
    
  4. FanDjango commented on Mar 6, 2023

    @FanDjango
    Collaborator

    Some more thoughts on this:

    Quite a few cases exist where the SSL Authentication itself does not fail, but shortly after, there is a "4xx" message saying that it was not possible to open a data connection.

    "Operation not permitted" is one such message, another actually refers to "session resume". There is a whole catalog of such messages, depending on the server type.

  5. 4nd3r5 commented on Mar 17, 2023

    @4nd3r5

    Is there a tracked issue in .net regarding this, we can subscribe to?

  6. FanDjango commented on Mar 17, 2023

    @FanDjango
    Collaborator

    @4nd3r5 You might want to read through this issue

    #948 (comment)

  7. FanDjango commented on Mar 21, 2023

    @FanDjango
    Collaborator
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      ⌂ 换网址