Re: general/4224: I get an inconsistend error, incomplete header sent error, but it works fine with ALL other browsers

[Dean Gaudet <dg...@arctic.org>]

The following reply was made to PR general/4224; it has been noted by GNATS.

From: Dean Gaudet <dg...@arctic.org>
To: John Saario <jo...@alamak.com.sg>
Cc: apbugs@apache.org
Subject: Re: general/4224: I get an inconsistend error, incomplete header sent error, but it works fine with ALL other browsers
Date: Sat, 1 May 1999 10:31:48 -0700 (PDT)

 Oh, you're running apache in inetd mode? 
 
 That mode probably has bugs... in fact I'm about to remove it from the
 server.  Try running apache in standalone mode please. 
 
 Dean
 
 On Wed, 28 Apr 1999, John Saario wrote:
 
 > Dean
 > 
 > I tried that by upgrading to apache 1.3.6 ... and putting in a no-keep alive for
 > IE 5.0 but same result.
 > 
 > KeepAlive On
 > MaxKeepAliveRequests 100
 > KeepAliveTimeout 15
 > BrowserMatch "Mozilla/2" nokeepalive
 > BrowserMatch "MSIE 4\.0b2;" nokeepalive downgrade-1.0 force-response-1.0
 > BrowserMatch "MSIE 5\.0;" nokeepalive downgrade-1.0 force-response-1.0
 > 
 > As long as I don't need to change any auth settings from default this should work?
 > 
 > Worse, and I have not yet reported this yet, but after 3 days apache 1.3.6 causes inetd
 > to lock up on FreeBSD .. I tried this both on FreeBSD 3.0 and 2.2.6. If I try to login
 > via telnet inetd bails with some pointer too low error. Restarting apache from the
 > console doesn't fix it. Hup of inetd doesn't fix it, but killing inetd and restarting it
 > does fix it. Of course server reboot will fix it as well. But anyway it doesn't show up
 > on my servers for about 3 days that boom, locked out. Pretty serious for me since I
 > am in Singapore and 5 of my servers are in the USA. Anyway, hope you can forward
 > that on. Still getting the "incomplete header information for all the IE 5.0 clients".
 > I switched back to apache_1.1.1 because of the inetd problem.
 > 
 > I didn't notice 1.3.6 seems to be as fast as older versions of apache and that is why
 > I liked it and upgraded ... I'll be watching for the next release to see if it's fixed since
 > I know most my servers are running very old ( but faster ) versions.