I didn't. But I just set that, and it didn't seem to make a
difference....
--Ryan
On Mon, 2003-06-09 at 14:16, Randy Kobes wrote:
> On Mon, 9 Jun 2003, Ryan Muldoon wrote:
>
> > Geoffrey,
> >
> > Thanks for the explanation. Unfortunately, I think I am
> > still a little unclear as to how to proceed. If I understand
> > you correctly, my first method is completely wrongheaded. (I
> > tried this because it is how the "Writing Apache Modules with
> > Perl and C" does it. p.327) So it sounds like the second way
> > is the appropriate usage for subprocess_env(). But it seems
> > like you're saying that I shouldn't be using that at all.
> > Specifically, here is what I'd like to get out of the
> > environment: SSL_CLIENT_S_DN_CN SSL_CLIENT_S_DN_O and things of
> > that nature. According to mod_ssl's documentation, these are
> > put in ENV upon processing of a client certificate. Ideally,
> > I'd like to make which fields to extract configurable, so I
> > don't want to hard-code.
> >
> > Currently, I have
> > PerlPassEnv SSL_CLIENT_S_DN_O
> > PerlPassEnv SSL_CLIENT_S_DN_CN
> > in my httpd.conf, but it doesn't seem to make any kind of difference.
> > To make sure it isn't just mod_ssl being lame for some reason, I've
> > tried it with DOCUMENT_ROOT and other standard ENV variables. But to no
> > avail. :(
>
> Do you have a
> SSLOptions +StdEnvVars
> directive inside the relevant location of your httpd.conf?
