[prev in list] [next in list] [prev in thread] [next in thread] 

List:       apache-modperl
Subject:    Re: modperl with SSL
From:       Clinton Gormley <clint () traveljury ! com>
Date:       2008-03-25 9:53:05
Message-ID: 1206438785.5312.16.camel () getafix ! traveljury ! com
[Download RAW message or body]

On Tue, 2008-03-25 at 17:45 +0800, J. Peng wrote:
> thanks.
> how about the capability of it?
> We have more than 100 million users,that's a great challenge.

That's a lot of users :)

I don't have the experience of supporting that number of users, but I've
used it on a site with 80 requests / second, and it didn't blink.  Load
was always low, memory usage minimal.

Searching google, it appears that you may need to increase the number of
fd's available to pound in that busy an environment, but otherwise, I
think it unlikely that you'll have any issues.

Clint
> 
> 
> On Tue, Mar 25, 2008 at 5:14 PM, Clinton Gormley <clint@traveljury.com> wrote:
> >
> > On Mon, 2008-03-24 at 15:25 +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.
> >  > modperl accept the SSL connection from clients, do the verification,
> >  > and if it's valid, redirect it to realserver with non-SSL (common
> >  > http) protocal.
> >  > Is it possible? if so, how to begin with it? at which stage?
> >  > Thanks in advance.
> >
> >  You could also use Pound (http://www.apsis.ch/pound) which I use in
> >  exactly the way described above.  Easy to set up, fast, stable, small.
> >
> >  clint
> >
> >

[prev in list] [next in list] [prev in thread] [next in thread]