Return-Path: owner-new-httpd Received: by taz.hyperreal.com (8.6.10/8.6.5) id KAA10181; Thu, 23 Mar 1995 10:02:19 -0800 Received: from uxc.cso.uiuc.edu by taz.hyperreal.com (8.6.10/8.6.5) with SMTP id KAA10170; Thu, 23 Mar 1995 10:02:16 -0800 Received: from fiction.isdn.uiuc.edu by uxc.cso.uiuc.edu with SMTP id AA05037 (5.67b8/IDA-1.5 for ); Thu, 23 Mar 1995 12:01:57 -0600 Received: (from blong@localhost) by fiction.isdn.uiuc.edu (8.6.9/8.6.9) id MAA19885 for new-httpd@hyperreal.com; Thu, 23 Mar 1995 12:03:45 -0600 Message-Id: <199503231803.MAA19885@fiction.isdn.uiuc.edu> Subject: Re: rst's votes on the current patches-for-0.2 To: new-httpd@hyperreal.com Date: Thu, 23 Mar 1995 12:03:44 -0600 (CST) In-Reply-To: <9503231400.AA08803@volterra> from "Robert S. Thau" at Mar 23, 95 09:00:25 am From: Brandon Long Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1556 Sender: owner-new-httpd@hyperreal.com Precedence: bulk Reply-To: new-httpd@hyperreal.com Last time, Robert S. Thau uttered the following other thing: > > E25_custom_error_responses: -1, until we've looked over the NCSA code > and decided what to do about it. > > NCSA 1.4 has what looks like a more general version of this; it > uses process_get to send the custom errors. This has more > overhead, but should let you do things like use a CGI script to > construct custom messages on the fly. My only concern with that > would be treatment of errors in the "GETs" of the error files, but > that is a solvable problem. (If you're already trying to send a > custom error message, further custom errors should be suppressed; > this may be happening already (I haven't checked) but a quick > once-over doesn't show code for it). > > However, if there's some good reason why the NCSA approach is the > wrong thing to do, I could be persuaded to change this vote. Already done that. Only took one complete machine crash to figure it out to. Notice the 'ErrorStat' global. It contains the last error on a connection, so that 2 errors in a row automatically switches to the builtin error functions. I guess I could have done something so that only two error messages of the same type can't be called in a row, but I thought this was safer. Brandon -- Brandon Long (N9WUC) "I think, therefore, I am confused." -- RAW Computer Engineering Run Linux 1.1.xxx It's that Easy. University of Illinois blong@uiuc.edu http://www.uiuc.edu/ph/www/blong Don't worry, these aren't even my views.