Return-Path: Delivered-To: apmail-httpd-dev-archive@www.apache.org Received: (qmail 12906 invoked from network); 14 Oct 2004 13:53:25 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 14 Oct 2004 13:53:25 -0000 Received: (qmail 82505 invoked by uid 500); 14 Oct 2004 13:52:13 -0000 Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 82403 invoked by uid 500); 14 Oct 2004 13:52:12 -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 82284 invoked by uid 99); 14 Oct 2004 13:52:10 -0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: domain of ast@domdv.de designates 193.102.202.1 as permitted sender) Received: from [193.102.202.1] (HELO hermes.domdv.de) (193.102.202.1) by apache.org (qpsmtpd/0.28) with ESMTP; Thu, 14 Oct 2004 06:52:08 -0700 Received: from [10.1.1.3] (helo=castor.lan.domdv.de) by zeus.domdv.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.42) id 1CI61W-0001Pu-Gc; Thu, 14 Oct 2004 15:52:06 +0200 Received: from pcast2.lan.domdv.de ([10.1.9.236]) by castor.lan.domdv.de with esmtpa (Exim 4.42) id 1CI61W-0000tO-DE; Thu, 14 Oct 2004 15:52:06 +0200 Message-ID: <416E8485.6000708@domdv.de> Date: Thu, 14 Oct 2004 15:52:05 +0200 From: Andreas Steinmetz User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20040918 X-Accept-Language: en-us, en, de MIME-Version: 1.0 To: dev@httpd.apache.org Subject: 2.1 CVS: ftp proxy probably broken X-Enigmail-Version: 0.86.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Did anybody notice that the ftp proxy seems to be broken? Any request returns 503 and the reason seems to be that ap_proxy_connect_backend is called with conn->addr=NULL from ap_proxy_ftp_handler. -- Andreas Steinmetz SPAMmers use robotrap@domdv.de