Delivered-To: new-httpd-archive@hyperreal.org Received: (qmail 8036 invoked by uid 6000); 3 Feb 2000 14:25:55 -0000 Received: (qmail 8026 invoked from network); 3 Feb 2000 14:25:52 -0000 Received: from alive.znep.com (root@207.167.15.58) by taz.hyperreal.org with SMTP; 3 Feb 2000 14:25:52 -0000 Received: from localhost (marcs@localhost) by alive.znep.com (8.9.3/8.9.1) with ESMTP id HAA27684 for ; Thu, 3 Feb 2000 07:25:51 -0700 (MST) (envelope-from marcs@znep.com) Date: Thu, 3 Feb 2000 07:25:51 -0700 (MST) From: Marc Slemko To: new-httpd@apache.org Subject: Re: cvs commit: apache-1.3/src/main http_core.c In-Reply-To: <20000203142239.6673.qmail@hyperreal.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: new-httpd-owner@apache.org Precedence: bulk Reply-To: new-httpd@apache.org Status: O On 3 Feb 2000 jim@hyperreal.org wrote: > jim 00/02/03 06:22:36 > > Modified: htdocs/manual/mod core.html directives.html > src CHANGES > src/main http_core.c > Log: > Streamline the AddDefaultCharset directive. Now this one directive > controls the entire 'charset' specification setup. If there is > heartburn, I have no trouble with backing this out, but it makes > live easier for those not using the "default" charset, and reduces > directive bloat a bit :) Is the use of "AddDefaultCharset default" perhaps a bit confusing because it refers to two different defaults? The first one is a default if there is no charset, the second is a default charset. Plus an implict third that it could refer to, which is the default setting of the directive? (I'm not saying back it out; if I wanted to -1 it I would have)