Three-minute timeout during surfing?

[pll at lanminds.com]

In a message dated: Mon, 26 Aug 2002 20:32:08 EDT
bscott at ntisys.com said:

>On Mon, 26 Aug 2002, at 12:09am, kena at well.com wrote:
>> Below is a snippet from an ethereal dump.  Any ideas?
>
>  Shutdown everything.  Place system on an isolated network.  Start packet
>sniffer (no filter).  Start any services Apache depends on (e.g., a local
>DNS resolver).  Start Apache.  Send a single web client request.  Watch to
>see if the system is sending any packets (other than the HTTP request).  If
>so, find out why, and see if the (lack of) response is the problem.  If not,
>the problem must be local -- database problem, maybe?

Ahhhm, just curious here, but why would a web server be sending out 
*any* packets, including HTTP requests.  Web servers *serve*, they 
don't request.  Good policy is to have an ip[chain,table]s script 
which prevents outgoing http requests from web servers.

If you're seeing requests *initiated* by your web server, you've got 
a major problem (unless it's something you specifically condone and 
(allowed to be) configured yourself.

-- 

Seeya,
Paul
--
	It may look like I'm just sitting here doing nothing,
   but I'm really actively waiting for all my problems to go away.

	 If you're not having fun, you're not doing it right!