rning how to avoid
abortive close. You have no choice in the matter but to follow Postel's
interoperability principle and be liberal in what you accept.
> -Original Message-
> From: owner-openssl-us...@openssl.org [mailto:owner-openssl-
> us...@openssl.org] On Behalf Of Donald J.
The server end appears to be GlobalScape EFT running on a windows
server.
I will summarize the IBM response:
When SSL is not involved, TCP will normally go through a graceful
connection teardown sequence where one side initiates the connection
closure by sending out a FIN. The other si
's response message to my last command. I don't remember off
the top of my head whether there's a straightforward FTP API on zOS.
--
Michael Wojcik
Technology Specialist, Micro Focus
> -Original Message-
> From: owner-openssl-us...@openssl.org [mailto:owner-ope
The FTP client is a batch mainframe process which
must get return code zero, or someone gets called
in the middle of the night. I have been working
with IBM support which claims that the server should
return a Fin before Rst. So I will probably turn this
problem over to our PC server group.
> -Original Message-
> From: owner-openssl-us...@openssl.org [mailto:owner-openssl-
> us...@openssl.org] On Behalf Of Donald J.
> Sent: Friday, 08 August, 2014 15:34
> To: openssl-users@openssl.org
> Subject: RST after close_notify
>
> I have an issue with an FTP client issuing a DIR comma
