catch SIGPIPE

[11419191]

SSL_shutdown() tries to send the close_notify shutdown alert to the peer. When the peer has shutdown, kernel will send a SIGPIPE to client, so we must catch the signal.

[anindyasen]

Hi @ismaell

1. Will the kernel always send SIGPIPE to the client on SSL_shutdown() or in some special scenario?
2. What will be the action on catching that signal?
3. How this scenario can be reproduced for testing purpose?
   Thanks

[ismaell]

1. SIGPIPE is received when the program tries to write to a closed connection.
2. The signal can be blocked.
3. You can implement a simple server that closes the connection immediately after accepting, that should cause the behaviour.

[satk0]

Hi @ismaell may I try to tackle this issue?

[ismaell]

Sure.

[satk0]

Hey @ismaell sorry for being idle for 2 weeks, but I was having a bad time building the axel project. It couldn't be built rn because of the zh_TW.po formatting issue:

Yet, I managed to solve it, check my PR: #447 😅