Re: mod_jk environment variable handling in Apache

[Henri Gomez <he...@gmail.com>]

Oups forgot to respond

The unique case where an env var could be usefull is by VirtualHost

>2006/11/23, Rainer Jung <ra...@kippdata.de>:
> Henri Gomez wrote:
> > I'm doing extensive use VirtualHost and no-jk directive on our Apache
> > 2.0.x servers so I'm very carefull about any changes in these area.
>
> There is one strange thing concerning apache and JkEnvVar. The mod_jk
> code handles them, as if it would make sense to have the same env var
> multiple times, with different default values. More precisely it uses
> "add table" instead of "set table" when JkEnvVar is being processed (so
> appending duplicates) and it also uses overlay tables to merge between
> base and vhost, which again appends all the base values to the vhost.
>
> This doesn't seem to make sense, because a servlet request attribute can
> only have one value.
>
> I would like to clean that up, so that later calls to JkEnvVar for the
> same variable overwrites earlier ones (using set table instead of add
> table), and all calls in vhost overwrite the ones in base (merging more
> carefully than table overlay does).
>
> Do you know any use case, where the current behaviour makes sense?
>
> I expect, that nobody really cared, because a config where the same env
> var is used with multiple default values doesn't really look reasonable.
>
> Regards,
>
> Rainer
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: dev-help@tomcat.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org