From: "Steven Levine" <ecs-isp@2rosenthals.com>
Message-ID: <6700b65a.11.mr2ice.fgrirsq@earthlink.net>
Date: Fri, 04 Oct 2024 20:45:30 -0700
To: "eCS ISP Mailing List" <ecs-isp@2rosenthals.com>
In-Reply-To: <list-11063065@2rosenthals.com>
Subject: Re: [eCS-ISP] SSL certs & apache 2.4.61

In <list-11063065@2rosenthals.com>, on 10/04/24
   at 10:47 PM, "Lewis G Rosenthal" <ecs-isp@2rosenthals.com> said:

Hi,

>Surely, that should work as well as my approach to move the conf to an 
>alternate directory, though ISTR some issue with checking variables in
>conf  files where the variable does not exist (faded memory from
>something we were  testing a couple decades ago, so perhaps I'm
>misremembering).

Are you thinking our PassEnv issue, which we ran into much more recently
than decades ago.  This thread, for some reason, triggered me to revist
the PassEnv issue where there appears to be no way to avoid a warning if
the environment variable is not defined.  

I got to refresh my knowledge of how If directive expressions worked along
with some not 100% obvious implementation issues related to httpd.conf
parsing.  The warnings are still there.  Unfortunately, the PassEnv
implementation checks if the variable exists when the PassEnv directive is
parsed, not when it is invoked.  This means it's not possible to wrap the
PassEnv in conditional code to avoid the warning or if there is, I have
not found it yet.

>As I said, that is the correct way to do this.

:-)

Steven

-- 
----------------------------------------------------------------------
"Steven Levine" <steve53@earthlink.net>  Warp/DIY/BlueLion etc.
www.scoug.com www.arcanoae.com www.warpcave.com
----------------------------------------------------------------------