Ian Ward Comfort wrote:
There isn't a problem with new directives. I merely suggested an
alternative that I think makes sense in this instance. Evidently not
everyone agrees. Bottom line: if you're doing the work, then you
decide what approach you prefer.
Fair enough. I'll keep an open mind in case a better suggestion
appears, and otherwise do something that works here.
Right now mod_proxy_ajp passes from r->subprocess_env all
key/val pairs having AJP_ prefix and stripping that prefix.
So one needs basically a duplicate value.
In your example
WEBAUTH_LDAP_DISPLAYNAME=foo
needs to be duplicated to
AJP_WEBAUTH_LDAP_DISPLAYNAME=foo
The solution might be to mark the
envvar so it gets evaluated at runtime
either as:
AJP_WEBAUTH_LDAP_DISPLAYNAME=${WEBAUTH_LDAP_DISPLAYNAME}
or even generic both for mod_proxy_http and mod_proxy_ajp
PROXY_WEBAUTH_LDAP_DISPLAYNAME=${WEBAUTH_LDAP_DISPLAYNAME}
So:
SetEnv PROXY_WEBAUTH_LDAP_DISPLAYNAME ${WEBAUTH_LDAP_DISPLAYNAME}
would cause to strip the PROXY_ from the r->subprocess_env and
use value from ${XX} again from r->subprocess_env.
Some other notion could be used of course, eg.
SetEnv PROXY_FOO
without a value (empty) could just use the FOO's value.
Regards
--
^(TM)
