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 ****
<!--#include virtual="header.html" -->
<H1 ALIGN="CENTER">Apache Server Frequently Asked Questions</H1>
<P>
! $Revision: 1.77 $ ($Date: 1997/06/30 21:42:26 $)
</P>
<P>
The latest version of this FAQ is always available from the main
--- 15,21 ----
<!--#include virtual="header.html" -->
<H1 ALIGN="CENTER">Apache Server Frequently Asked Questions</H1>
<P>
! $Revision: 1.78 $ ($Date: 1997/07/05 15:01:17 $)
</P>
<P>
The latest version of this FAQ is always available from the main
***************
*** 162,167 ****
--- 162,170 ----
<LI><A HREF="#nodelay">Why am I getting "<SAMP>httpd: could not
set socket option TCP_NODELAY</SAMP>" in my error log?</A>
</LI>
+ <LI><A HREF="#peerreset">Why am I getting "<SAMP>connection
+ reset by peer</SAMP>" in my error log?</A>
+ </LI>
<LI><A HREF="#nph-scripts">How can I get my script's output without
Apache buffering it?</A>
</LI>
***************
*** 1130,1135 ****
--- 1133,1152 ----
before Apache reached the point of calling <CODE>setsockopt()</CODE>
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.
+ </P>
+ <HR>
+ </LI>
+ <LI><A NAME="peerreset">
+ <STRONG>Why am I getting "<SAMP>connection reset by
+ peer</SAMP>" in my error log?</STRONG>
+ </A>
+ <P>
+ 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.
</P>
<HR>
</LI>
