Return-Path: Delivered-To: apmail-httpd-dev-archive@www.apache.org Received: (qmail 87656 invoked from network); 10 Dec 2003 20:12:18 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 10 Dec 2003 20:12:18 -0000 Received: (qmail 62211 invoked by uid 500); 10 Dec 2003 20:12:02 -0000 Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 62158 invoked by uid 500); 10 Dec 2003 20:12:01 -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 62144 invoked from network); 10 Dec 2003 20:12:01 -0000 Received: from unknown (HELO hqvwall01.citrix.com) (12.8.192.38) by daedalus.apache.org with SMTP; 10 Dec 2003 20:12:01 -0000 Received: from ftlpexch5im01.citrix.com ([10.9.1.140]) by hqvwall01 with tre nd_isnt_name_B; Wed, 10 Dec 2003 15:11:49 -0500 Received: by ftlpexch5im01 with Internet Mail Service (5.5.2656.59)id ; Wed, 10 Dec 2003 15:11:43 -0500 Message-ID: <8615FFA58F144C4DAC79966ADFC04EE5C50512@ftlpexch503> From: Larry Toppi To: "'dev@httpd.apache.org'" Subject: RE: Mem Leak when reverse proxying HTTP post requests Date: Wed, 10 Dec 2003 15:11:33 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2656.59) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C3BF59.BECFA660" X-imss-version: 2.0 X-imss-result: Passed X-imss-scores: Baseline:45.3767 C:12 M:1 S:5 R:5 X-imss-settings: Clean:4 C:4 M:4 S:4 R:1 (0.1000 0.1000) X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C3BF59.BECFA660 Content-Type: text/plain Thanks. -----Original Message----- From: Jeff Trawick [mailto:trawick@attglobal.net] Sent: Wednesday, December 10, 2003 2:46 PM To: dev@httpd.apache.org Subject: Re: Mem Leak when reverse proxying HTTP post requests Larry Toppi wrote: > I found the culprit. The EOS bucket was being removed from the brigade > but not destroyed. I'm going to submit the following patch to fix this bug. patch mangled just a teeny weeny bit to fit with changes to that code in 2.1-dev, then committed to 2.1-dev... I'll suggest your patch for backporting to stable branch for 2.0.next. ------_=_NextPart_001_01C3BF59.BECFA660 Content-Type: text/html RE: Mem Leak when reverse proxying HTTP post requests

Thanks.

-----Original Message-----
From: Jeff Trawick [mailto:trawick@attglobal.net]
Sent: Wednesday, December 10, 2003 2:46 PM
To: dev@httpd.apache.org
Subject: Re: Mem Leak when reverse proxying HTTP post requests

Larry Toppi wrote:
> I found the culprit.  The EOS bucket was being removed from the brigade
> but not destroyed.  I'm going to submit the following patch to fix this bug.

patch mangled just a teeny weeny bit to fit with changes to that code in
2.1-dev, then committed to 2.1-dev...  I'll suggest your patch for backporting
to stable branch for 2.0.next.

------_=_NextPart_001_01C3BF59.BECFA660--