It only now occurred to me that these exceptions do not actually trigger a log message, they only call ResponseExceptionHandler, which means it’s up to the server (Propeller in my case) to deal with it

Author: Timwi

Src/HttpServer.cs

@@ -494,18 +494,6 @@ private void asyncCallbackTryBlock(IAsyncResult ar, SslStream secureStream)
             {
                 secureStream.EndAuthenticateAsServer(ar);
             }
-            catch (IOException io) when (io.Message == "Authentication failed because the remote party has closed the transport stream.")
-            {
-                // Very common exception that appears to be harmless
-                Socket.Close();
-                return;
-            }
-            catch (AuthenticationException auth) when (auth.Message == "Cannot determine the frame size or a corrupted frame was received.")
-            {
-                // Very common exception that appears to be harmless
-                Socket.Close();
-                return;
-            }
             catch (Exception e)
             {
                 Socket.Close();