hello list,
we have our own realserver called QHttpd.
This realserver doesn't support SSL protocal (https).
So I have to develop a proxy before QHttpd to get it be compatible with SSL.
I was thinking using modperl handler to do it.
modperl accept the SSL connection from clients, do the
What is a realserver?
J. Peng wrote:
hello list,
we have our own realserver called QHttpd.
This realserver doesn't support SSL protocal (https).
So I have to develop a proxy before QHttpd to get it be compatible with SSL.
I was thinking using modperl handler to do it.
modperl accept the SSL
a backend server - the server that REALly serves the request.
Foo JH wrote:
What is a realserver?
J. Peng wrote:
hello list,
we have our own realserver called QHttpd.
This realserver doesn't support SSL protocal (https).
So I have to develop a proxy before QHttpd to get it be compatible
On Mon, Mar 24, 2008 at 03:25:26PM +0800, J. Peng wrote:
hello list,
we have our own realserver called QHttpd.
This realserver doesn't support SSL protocal (https).
So I have to develop a proxy before QHttpd to get it be compatible with SSL.
I was thinking using modperl handler to do it.
I also recommend stunnel. It has come through for me in these same
situations without problems.
On Mon, 2008-03-24 at 07:46 -0400, Roberto C. Sánchez wrote:
On Mon, Mar 24, 2008 at 03:25:26PM +0800, J. Peng wrote:
hello list,
we have our own realserver called QHttpd.
This realserver
I'm trying to create a custom block directive, following the
documentation in the ModPerl2 book (or the on-line documentation). The
minimal code for the problem I am seeing is below. I have the following
block in apache2.conf for the new block StdVHost ... and the module is
in the