Received: (from majordom@localhost) by hyperreal.org (8.8.5/8.8.5) id IAA23431; Sat, 5 Jul 1997 08:01:21 -0700 (PDT) Received: (from coar@localhost) by hyperreal.org (8.8.5/8.8.5) id IAA23426 for apache-cvs; Sat, 5 Jul 1997 08:01:19 -0700 (PDT) Date: Sat, 5 Jul 1997 08:01:19 -0700 (PDT) From: Rodent of Unusual Size Message-Id: <199707051501.IAA23426@hyperreal.org> To: apache-cvs@hyperreal.org Subject: cvs commit: apache/htdocs/manual/misc FAQ.html Sender: apache-cvs-owner@apache.org Precedence: bulk Reply-To: new-httpd@apache.org coar 97/07/05 08:01:19 Modified: htdocs/manual/misc FAQ.html Log: Add FAQ about "connection reset by peer" message. Revision Changes Path 1.78 +18 -1 apache/htdocs/manual/misc/FAQ.html Index: FAQ.html =================================================================== RCS file: /export/home/cvs/apache/htdocs/manual/misc/FAQ.html,v retrieving revision 1.77 retrieving revision 1.78 diff -C3 -r1.77 -r1.78 *** FAQ.html 1997/06/30 21:42:26 1.77 --- FAQ.html 1997/07/05 15:01:17 1.78 *************** *** 15,21 ****

Apache Server Frequently Asked Questions

! $Revision: 1.77 $ ($Date: 1997/06/30 21:42:26 $)

The latest version of this FAQ is always available from the main --- 15,21 ----

Apache Server Frequently Asked Questions

! $Revision: 1.78 $ ($Date: 1997/07/05 15:01:17 $)

The latest version of this FAQ is always available from the main *************** *** 162,167 **** --- 162,170 ----

  • Why am I getting "httpd: could not set socket option TCP_NODELAY" in my error log?
  • +
  • Why am I getting "connection + reset by peer" in my error log? +
  • How can I get my script's output without Apache buffering it?
  • *************** *** 1130,1135 **** --- 1133,1152 ---- before Apache reached the point of calling setsockopt() for the connection. It shouldn't occur for more than about 1% of the requests your server handles, and it's advisory only in any case. +

    +
    + +
  • + Why am I getting "connection reset by + peer" in my error log? + +

    + This is a normal message and nothing to be alarmed about. It simply + means that the client cancelled the connection before it had been + completely set up - such as by the end-user pressing the "Stop" + button. People's patience being what it is, sites with response-time + problems or slow network links may experiences this more than + high-capacity ones or those with large pipes to the network.