On Fri, Jul 10, 2015 at 12:07 PM, Macks, Aaron
<amacks@xxxxxxxxxxxxxxxxxxx> wrote:
> one for every time we use any of those variables. We tried setting a
> default value with SetEnv, then overwriting it with setenvif, but that
> didn’t fix anything. What should we tweek in the configs to conform to the
> 2.4 way and tamp down the useless warnings?
You could set native envvar ASAPPSERVER to ${ASAPPSERVER} before you
invoke apachectl, or in the envvars script it usually sources. It's a
current limitation that the syntax for variables interpolated at
startup overlaps with this runtime variable interpolation.
Your config might inadvertently disable reuse of backend connections
unless you statically list off ProxyPass for each dynamic one that
might be used. See the discussion of workers in the mod_proxy doc.
--
Eric Covener
covener@xxxxxxxxx
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|