> Try the suggestions for getting a baktrace from:
> http://www.modssl.org/docs/2.6/ssl_faq.html#report-backtrace
We're not using gcc/gdb but HP's cc and xdb. I'm working on making
the debugger produce a backtrace.
> > It's like this:
> >
> > http https
> > Browser ------> Server1 -------> Server2
> >
> > Server2 is configured to require client authetication, and
> > Server1 is configured with a proxy client cert.
> >
>Just out of curiosity - the connection from the browser to server1 -
>is that as a proxy or is it reverse proxying?
Actually, I'm not sure. I'm not that experienced with proxy stuff.
The browser is NOT configured to use Server1 as a proxy.
Maybe I have misunderstood something. What I want to achieve is that
the user (Browser) connects to Server1 as it would to any normal web
server. Then I want Server1 to transparently fetch data from Server2
using https. For this I have configured:
ProxyPass /appname https://Server2:port/appname
Maybe there is another way of doing this? But anyway, there clearly is
a bug in mod_ssl which I would like to help tracking down.
> > [info] Init: Configuring temporary DH parameters (512/1024 bits)
>
> DH? do you have both RSA and DH certs?
No, we only use RSA certs. I don't know why this DH stuff is printed.
> Remember that the SSL proxy features are "experimental".
Sure, I am aware of that.
--
Mats Josefsson ([EMAIL PROTECTED])
RSV IT
Mail to the address above will not be forwarded. If you want
to reach me when I'm not at RSV, use "[EMAIL PROTECTED]" instead.
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
