Return-Path: Delivered-To: apache-bugdb-archive@hyperreal.org Received: (qmail 24733 invoked by uid 6000); 27 Jan 1999 19:00:03 -0000 Received: (qmail 24689 invoked by uid 2001); 27 Jan 1999 19:00:01 -0000 Date: 27 Jan 1999 19:00:01 -0000 Message-ID: <19990127190001.24688.qmail@hyperreal.org> To: apache-bugdb@apache.org Cc: apache-bugdb@apache.org, From: Marc Slemko Subject: RE: general/3724: Frequently receiving error 'Server Returned an Invalid Response' in Internet Explorer or 'Server returned no data' in N e tscape Reply-To: Marc Slemko Sender: apache-bugdb-owner@apache.org Precedence: bulk The following reply was made to PR general/3724; it has been noted by GNATS. From: Marc Slemko To: "Thomas, Chad A." Cc: "'apbugs@Apache.Org'" Subject: RE: general/3724: Frequently receiving error 'Server Returned an Invalid Response' in Internet Explorer or 'Server returned no data' in N e tscape Date: Wed, 27 Jan 1999 11:01:06 -0800 (PST) On Wed, 27 Jan 1999, Thomas, Chad A. wrote: > I am currently undergoing extensive development of this machine and cannot > afford to run without mod_perl. I may be able to test in a few weeks. This sounds a lot like it would be a mod_perl issue to me. > > Lately, the problem has only happened first thing in the morning and then > has been fine the rest of the day. Could it be caused by the server > processes being idle to long? If I click reload about 5 or 6 times, the > error message eventually goes away. I am no mod_perl expert, but I have certainly heard of various things like this happening with mod_perl in certain situations. > > > ---------- > > From: Marc Slemko[SMTP:marcs@znep.com] > > Sent: Tuesday, January 26, 1999 12:38 AM > > To: Thomas, Chad A. > > Cc: 'apbugs@Apache.Org' > > Subject: RE: general/3724: Frequently receiving error 'Server > > Returned an Invalid Response' in Internet Explorer or 'Server returned > > no data' in N e tscape > > > > On Mon, 25 Jan 1999, Thomas, Chad A. wrote: > > > > > Still experiencing problems after upgrading to Apache 1.3.4 and mod_perl > > > 1.17. > > > > Once again, does the same thing happen WITHOUT mod_perl compiled into the > > server. > > >