Feature Request: provide a milllisecond delay parameter to session termination after 'Goodbye.'
|Reported by:||Steve Fox||Owned by:|
|Keywords:||goodbye. Session destroyed||Cc:||Steve Fox|
|Component version:||1.1.0||Operating system type:|
|Operating system version:||Server 2012r2|
We have a contact using a 'slow' system that sends us small EDI files and after our upgrade to 1.1.0 started to received errors at the end of the session.
We suspect that during the session termination protocol Filezilla closes the socket quickly - creating a socket termination error on their side because they are still processing the 'Goodbye.' acknowledgement
Would you please consider adding a timeout value in MS (up to say, 5000 or more) in the configuration to allow for the client to process and disconnect from their side prior to the session destroy? Everything still works, but it generates a non-critical error for each session
2021-12-23T18:45:25.704Z >> [FTP Session 858 188.8.131.52 wfm_prod] QUIT
2021-12-23T18:45:25.704Z << [FTP Session 858 184.108.40.206 wfm_prod] 200 Goodbye.
- REQUEST FOR A TIME OUT HERE
2021-12-23T18:45:25.704Z II [FTP Session 858 220.127.116.11] Session 0x2d44db7560 with ID 858 destroyed.
2021-12-23T18:47:39.812Z II [FTP Session 859 18.104.22.168] Session 0x2d44db7560 with ID 859 created.