On Wed, Jan 13, 1999, Khimenko Victor wrote:
> > This time I'm a little bit faster with mod_ssl than we're with Apache itself,
> > but the next days I'm busy with other stuff and I've already prepared it the
> > last two days, so push it out now. Of course you've to wait a few more hours
> > until we've the Apache tarball in place.
>
> Ok, this is updated EAPIk for 2.1.7 ... When doing this update I found strange
> thing :
> -- cut --
> [khim@khim mod_ssl-2.1.7-1.3.4]$ grep ssl::verify `find -type f`
> ./pkg.sslmod/ssl_engine_ext.c: result =
>ap_ctx_get(r->connection->client->ctx, "ssl::verify::errcode");
> ./pkg.sslmod/ssl_engine_ext.c: result =
>ap_ctx_get(r->connection->client->ctx, "ssl::verify::errstr");
> [khim@khim mod_ssl-2.1.7-1.3.4]$
> -- cut --
>
> What's this ? What's purpose of this ap_ctx_get(..., "ssl::verify::errcode");
> and ap_ctx_get(..., "ssl::verify::errstr"); if the whole mod_ssl 2.1.7 package
> do not have neither ap_ctx_set(..., "ssl::verify::errcode", ...); nor
> ap_ctx_set(..., "ssl::verify::errstr", ...); ? How this could be usefull ?
It doesn't harm, but it's not useful, of course. Seems like I've thought I can
provide the %{errcode}c and %{errstr}c variables for mod_log_config, so I've added the
ap_ctx_get for them. But then I've forgot to provide the variables over time.
It's now fixed for mod_ssl 2.1.8. Thanks for the hint.
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/
Official Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
