Return-Path: Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 91752 invoked by uid 500); 27 Feb 2003 01:43:43 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 91737 invoked from network); 27 Feb 2003 01:43:43 -0000 Message-ID: <3E5D6CFE.8040800@stason.org> Date: Thu, 27 Feb 2003 12:42:22 +1100 From: Stas Bekman Organization: Hope, Humanized User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020826 X-Accept-Language: en-us, en MIME-Version: 1.0 To: dev@httpd.apache.org Subject: Re: cvs commit: httpd-2.0 CHANGES References: <20030226190300.6835.qmail@icarus.apache.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N wrowe@apache.org wrote: > wrowe 2003/02/26 11:03:00 > > Modified: . CHANGES > Log: > Brad, Stas, I presume these patches were first committed to 2.1-dev. > Please keep the CHANGES logs in sync! Duh! Sorry for being a troublemaker. I thought that CHANGES in the dev tree includes only CHANGES which weren't backported to the stable tree. At least that's what the header says: [Remove entries to the current 2.0 section below, when backported] since I've immediately committed to the stable tree, instead of adding and immediately removing, I skipped adding in first place. I suppose the add/remove is important for cvs logs, which I've missed to see. Will do that in the future. > Revision Changes Path > 1.1090 +13 -1 httpd-2.0/CHANGES > > Index: CHANGES > =================================================================== > RCS file: /home/cvs/httpd-2.0/CHANGES,v > retrieving revision 1.1089 > retrieving revision 1.1090 > diff -u -r1.1089 -r1.1090 > --- CHANGES 25 Feb 2003 22:59:56 -0000 1.1089 > +++ CHANGES 26 Feb 2003 19:02:59 -0000 1.1090 > @@ -135,9 +135,21 @@ > > Changes with Apache 2.0.45 > > + *) Enhance the behavior of mod_isapi's WriteClient() callback to > + provide better emulation for isapi modules that presume that the > + first WriteClient() call may send status and headers. An example > + of WriteClient() abuse is the foxisapi module, which relies on > + that assumpion and now works. [William Rowe, Milan Kosina] > + > + *) Check the return value of ap_run_pre_connection(). So if the > + pre_connection phase fails (without setting c->aborted) > + ap_run_process_connection is not executed. [Stas Bekman] > + > *) Fixed a problem with mod_ldap which caused it to fault when caching > was disabled. Needed to make sure that the code did not > - attempt to use the cache if it didn't exist. [Brad Nicholes] > + attempt to use the cache if it didn't exist. Also fixed some memory > + leaks which were due to not releasing LDAP resources on error > + conditions. [Brad Nicholes] > > *) Hook mod_proxy's fixup before mod_rewrite's fixup, so that by > mod_rewrite proxied URLs will not be escaped accidentally by > > > -- __________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:stas@stason.org http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com