At 08:05 AM 8/2/01, you wrote:
>Does anyone know the status of nsvhr? It does not appear in the current
>release and the code on sourceforge appears to be about 6 months old.
>
>I was thinking about using it to build an SSL proxy. That way I could have a
>set of servers to handle SSL connections and load balance the requests back
>to a set of servers not running SSL. That way I can have one SSL client
>session talking to multiple servers on the server side.
>
>Has anyone tried this or have any other suggestions?
nsvhr pretty much works out of the box these days. If you don't want to
use my patches, do incorporate Dossy's latest fix sometime before you go
into production. (not needed for prototyping and testing.)
Most people want to use nsvhr and offer separate server certificates. No
one knows how that might be done. But offering all users the same
certificate and just load balancing, well, that should work. So off the
top of my head, I would think that what you want to do might be a possible
todo with no modifications (and would be a very cool thing to try).
An AOLserver using nsvhr typically gets its incoming connections from
another driver (nssock, right), and just deals with the proxying of it. It
copies the data from the backend and sends it back to the client using the
conn's driver, so I would think it should work just fine when the incoming
connection is nsopenssl or nsssl.
Let me know how it works (or doesn't work....)
Jerry
=====================================================
Jerry Asher [EMAIL PROTECTED]
1678 Shattuck Avenue Suite 161 Tel: (510) 549-2980
Berkeley, CA 94709 Fax: (877) 311-8688
