On Tue, May 18, 1999, Andrea e Luca Giacobazzi wrote:
> >Wait. First: Yes, you should set the env-var via
> >ap_table_get(r->subprocess_env,...). Second: you've to use %{ENV:<name>}
> or
> >add your variable to ssl_engine_vars.c.
>
> I see that SSLRequire works well on my ApacheSSL (of course), but the env
> var I created (OCSP_RESPONSE_STATUS) is not visible from the SSLRequire
> check, but is visible from a cgi-bin I created to print out env vars.
> Exactly the cgi-bin print out the env vars concerning client authentication
> (so mine var too) correctly, just if I activate SSLVerifyClient *outside*
> the </Directory> statements group; cgi-bin doesn't print env vars if I
> activate SSLVerifyClient inside the </Directory> statements group.
> I added the new env var to the structure ssl-fixup..vars[], and i set the
> value with the statement:
>
> ap_table_set(r->subprocess_env, "OCSP_RESPONSE_STATUS", "value string");
>
> in ssl_engine_kernel.c
> Is correct ? How can I correctly add an env var (in ssl_engine_vars.c) ?
Err? When you already found ssl_engine_vars.c I wonder why you still ask how
you can add it? It's a plain waterfall model inside this source. The variable
name is parsed from the beginning and when a prefix is found, the lookup is
directed to a subfunction, etc. This way the whole namespace is provided. In
your case you would match "OCSP_" in the top-level lookup function and call a
subfunction with the remaining part. Then in the sub-function for OCSP you do
your magic, i.e. you match "RESPONSE_STATUS" and give out the results, etc.
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
