Return-Path: Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 27631 invoked by uid 500); 23 Apr 2002 21:00:06 -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 27614 invoked from network); 23 Apr 2002 21:00:05 -0000 Date: Tue, 23 Apr 2002 16:57:28 -0400 (EDT) From: Cliff Woolley X-X-Sender: root@deepthought.cs.virginia.edu To: dev@httpd.apache.org Subject: Re: [Bug 8407] - reverse proxy return FORBIDDEN all the time In-Reply-To: <20020423172517.18221.qmail@nagoya.betaversion.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On 23 Apr 2002 bugzilla@apache.org wrote: > http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8407 > reverse proxy return FORBIDDEN all the time > > ------- Additional Comments From pascal.barbedor@laposte.net 2002-04-23 17:25 ------- > I loaded additionnal mod_proxy modules (mod_proxy_http.so, mod_proxy_ftp.so, > and/or mod_proxy_connect.so )and it works now... > the error log said nothing. We should consider having mod_proxy issue a warning at startup if it's loaded as a DSO but none of the protocol handlers (mod_proxy_*.so) are loaded. I think you get an message when you try the connect, but that might only show up at high LogLevels (not sure on that one... I've seen it, this guy didn't). Anyway, this problem has bitten me before when I switched from a static mod_proxy [where the mod_proxy_foo's are built in by default] to a shared one, where they're built by default but you have to LoadModule them individually. --Cliff -------------------------------------------------------------- Cliff Woolley cliffwoolley@yahoo.com Charlottesville, VA