Avoid crashing on SIGPIPE

Under some circumstances, clients could cause SIGPIPE to slcl. Since
this signal was not handled by server.c (i.e., via sigaction(3)), slcl
would crash without any error messages printed to stderr.

In such situation, SIGPIPE should not be usually considered a fatal
error, so it is preferrable to close the connection and keep working.

1 files changed, 2 insertions, 0 deletions

diff --git a/http.c b/http.c
index 501499b..d843bb5 100644
--- a/http.c
+++ b/http.c
@@ -496,6 +496,8 @@ static int rw_error(const int r, bool *const close)
     {
         switch (errno)
         {
+            case EPIPE:
+                /* Fall through. */
             case ECONNRESET:
                 *close = true;
                 return 1;