Received: by taz.hyperreal.com (8.6.12/8.6.5) id MAA13179; Fri, 5 Jul 1996 12:31:43 -0700 Received: from ooo.lanl.gov by taz.hyperreal.com (8.6.12/8.6.5) with ESMTP id MAA13173; Fri, 5 Jul 1996 12:31:41 -0700 Received: by ooo.lanl.gov (1.37.109.16/16.2) id AA196875090; Fri, 5 Jul 1996 13:31:30 -0600 From: Rob Hartill Message-Id: <199607051931.AA196875090@ooo.lanl.gov> Subject: Re: SetEnv To: new-httpd@hyperreal.com Date: Fri, 5 Jul 96 13:31:30 MDT In-Reply-To: <199607051921.UAA00327@aaaaaaaa.demon.co.uk>; from "Andrew Wilson" at Jul 5, 96 8:21 pm X-Organization: Theoretical Division, T-8. Los Alamos National Laboratory X-Snail: LANL Theoretical Divi' T-8, MS B285, P.O Box 1663, Los Alamos NM 87545 X-Marks-The-Spot: Doh ! X-Url: http://nqcd.lanl.gov/~hartill/ X-Cessive-Use-Of-Headers: check Mailer: Elm [revision: 70.85] Sender: owner-new-httpd@apache.org Precedence: bulk Reply-To: new-httpd@hyperreal.com Andy wrote: > 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... Then why does mod_env.c have an example in the headers... * For example, the sequence: * PassEnv PATH * SetEnv PATH /special/path * Causes PATH to take the value '/special/path'. That must count as a severe documentation bug... it uses an example that's known not to work. Andy you're a cruel bugger! :-) blue in the face, rob -- The rumor is that Jack Kevorkian has setup a Windows-NT users group.