Please sign in to comment.
Removing the sending of the QUIT command to the server: The server do…
…es not have an implementation of this. Causes an issue of the server throwing Connection reset by peer Explanation: Client establishes socket Client sends command (next, update, peek, etc) Client waits for response Server sends response (+OK, -ERROR, etc) Client receives response Client sends QUIT Client closes socket Server receives QUIT Server responds -ERROR (valid error handling because QUIT is not a valid command) - Socket is closed so server throws ECONNECTRESET (and a SIGPIPE I think) Server handles a few of these alright, but if the server is being sent commands a lot then the errors get stacked quickly and the eventual effect is a Seg Fault
- Loading branch information...