Received: by taz.hyperreal.com (8.6.12/8.6.5) id MAA12477; Fri, 5 Jul 1996 12:23:29 -0700 Received: from relay-4.mail.demon.net by taz.hyperreal.com (8.6.12/8.6.5) with SMTP id MAA12462; Fri, 5 Jul 1996 12:23:26 -0700 Received: from post.demon.co.uk ([158.152.1.72]) by relay-4.mail.demon.net id ag29087; 5 Jul 96 19:23 GMT Received: from aaaaaaaa.demon.co.uk ([158.152.178.85]) by relay-3.mail.demon.net id aa13590; 5 Jul 96 20:22 +0100 Received: (from andrew@localhost) by aaaaaaaa.demon.co.uk (8.7.5/8.6.9) id UAA00327 for new-httpd@hyperreal.com; Fri, 5 Jul 1996 20:21:10 +0100 (BST) From: Andrew Wilson Message-Id: <199607051921.UAA00327@aaaaaaaa.demon.co.uk> Subject: Re: SetEnv To: new-httpd@hyperreal.com Date: Fri, 5 Jul 1996 20:21:09 +0100 (BST) In-Reply-To: <199607051843.AA156352200@ooo.lanl.gov> from "Rob Hartill" at Jul 5, 96 12:43:19 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8891-1 Content-Transfer-Encoding: 7bit Sender: owner-new-httpd@apache.org Precedence: bulk Reply-To: new-httpd@hyperreal.com You'll find that PATH and TZ (timezone) are special cased by the core. This means that you can SetEnv both variables till you're blue in the face but the core will ignore your settings and impose its own. Seems like the core code is called after mod_env.c has set the values. One fix is to make the core only supply values if they're not already in the environment (put there by mod_env.c forinstance). Another fix is to remove the core's ENV variable setting abilities and instead rely on mod_env.c for talking to the server's real (or virtual) ENVironment. But people have mentioned this before so... Ay. > Has anyone managed to override the PATH using SetEnv/PassEnv/etc ? > > When I try it, the exisiting path is always kept and my new path is > ignored. > > > ?