diff --git a/CHANGES b/CHANGES
index 0ac5f02a..2d7e66f0 100644
--- a/CHANGES
+++ b/CHANGES
@@ -2,6 +2,10 @@
 22 Feb 2006 - 2.1.0-rc7+
 ------------------------
 
+* Removed the "Connection reset by peer" message, which has nothing
+  to do with us. Actually the message was downgraded from ERROR to
+  NOTICE so it will still appear in the debug log.
+
 * Removed the (harmless) message mentioning LAST_UPDATE_TIME missing.
 
 * It was not possible to remove a rule placed in phase 4 using
diff --git a/apache2/apache2_io.c b/apache2/apache2_io.c
index 6e2cee24..ab130ceb 100644
--- a/apache2/apache2_io.c
+++ b/apache2/apache2_io.c
@@ -569,8 +569,20 @@ apr_status_t output_filter(ap_filter_t *f, apr_bucket_brigade *bb_in) {
 
         rc = ap_pass_brigade(f->next, msr->of_brigade);
         if (rc != APR_SUCCESS) {
-            msr_log(msr, 1, "Output filter: Error while forwarding response data (%i): %s",
-                rc, get_apr_error(msr->mp, rc));
+            int log_level = 1;
+
+            if (APR_STATUS_IS_ECONNRESET(rc)) {
+                /* Message "Connection reset by peer" is common and not a sign
+                 * of something unusual. Hence we don't want to make a big deal
+                 * about it, logging at NOTICE level. Everything else we log
+                 * at ERROR level.
+                 */
+                log_level = 3;
+            }            
+
+            msr_log(msr, log_level, "Output filter: Error while forwarding response data (%i): %s",
+                    rc, get_apr_error(msr->mp, rc));
+
             return rc;
         }
     }