Mailing-List: contact users-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@httpd.apache.org
Received-SPF: pass (nike.apache.org: local policy)
Date: Thu, 1 Mar 2012 17:19:37 +0100
From: Juergen Daubert <jue@jue.li>
To: users@httpd.apache.org
Message-ID: <20120301161937.GA8722@jue.netz>
References: <20120301113422.GA7521@jue.netz>
 <20120301153810.5155c12a@baldur>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20120301153810.5155c12a@baldur>
User-Agent: Mutt/1.5.21 (2010-09-15)
Subject: Re: [users@httpd] apache 2.4.1, regression, caching forward proxy
 configuration

On Thu, Mar 01, 2012 at 03:38:10PM +0000, Nick Kew wrote:
> On Thu, 1 Mar 2012 12:34:22 +0100
> Juergen Daubert <jue@jue.li> wrote:
> 
> > Any ideas or suggestions?
> 
> Set Loglevel to debug, or if necessary high-level trace,
> for the relevant modules.

Thanks for the hint but I've tried that already, with no result.

Even with a 

LogLevel cache:trace8
LogLevel cache_disk:trace8

there's nothing in the logfile. To verify the syntax I've done the 
same for the proxy module with proxy:trace8 which works, meaning a 
lot of traces in the logfile.

The strange thing is that everything works with apache 2.2.x, so
my guess is that there are either new but undocumented configuration
switches or we have a regression in 2.4.1. 
BTW, I've found another report for probably the same issue, see [1].


Thanks and regards
Juergen

[1] http://article.gmane.org/gmane.comp.apache.user/98771


---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org