Francois PIETTE wrote: >>> The server can't be sure the file has been sent properly before the >>> connection is properly closed. > >> That's true, however he knows that he sent all, he cannot know >> whether it all received at the peer. > > He knows data is correctly received by the peer because of the > graceful close sequence initiated by Shutdown. If there is a problem > with the client, the problem will be reported as an error in the > FD_CLOSE message that follow.
I wonder why Serv-U sends the RETR response at once, right after Data.ShutDown(1). RFC say that the server is responsible to close the data connection (in non-passive mode). From the view of the server all data has been sent at the moment when Data.ShutDown(1) is called, which also marks EOF since no more data will follow. My experience is that Serv-U always was very close to the RFCs, including the SSL stuff. However I'm not 100% sure since the RFC are not very specific in how one has to interpret the expression "close the connection". IMHO initiation of a gracefull shutdown may be interpreted as a close, if not, calling ShutDown() (which finally makes the client close the connection) wasn't RFC conform. -- Arno Garrels [TeamICS] http://www.overbyte.be/eng/overbyte/teamics.html > > > -- > Contribute to the SSL Effort. Visit > http://www.overbyte.be/eng/ssl.html -- > [EMAIL PROTECTED] > http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
