Return-Path: Delivered-To: apmail-httpd-users-archive@www.apache.org Received: (qmail 43770 invoked from network); 7 Feb 2011 12:01:54 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 7 Feb 2011 12:01:54 -0000 Received: (qmail 69894 invoked by uid 500); 7 Feb 2011 12:01:51 -0000 Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 69685 invoked by uid 500); 7 Feb 2011 12:01:48 -0000 Mailing-List: contact users-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: users@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@httpd.apache.org Received: (qmail 69677 invoked by uid 99); 7 Feb 2011 12:01:47 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 07 Feb 2011 12:01:47 +0000 X-ASF-Spam-Status: No, hits=0.7 required=5.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [194.126.126.41] (HELO smtp-out.neti.ee) (194.126.126.41) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 07 Feb 2011 12:01:39 +0000 Received: from localhost (localhost [127.0.0.1]) by vm-relay7.estpak.ee (Postfix) with ESMTP id 99CB7CF3; Mon, 7 Feb 2011 14:01:17 +0200 (EET) X-Virus-Scanned: Debian amavisd-new at vm-relay7.estpak.ee Received: from smtp-out.neti.ee ([127.0.0.1]) by localhost (vm-relay7.estpak.ee [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pygxjBA6iCQx; Mon, 7 Feb 2011 14:01:13 +0200 (EET) Received: from NETI-Relayhost1.estpak.ee (neti-relayhost1.estpak.ee [88.196.174.198]) by vm-relay7.estpak.ee (Postfix) with ESMTP id E4EABCEE; Mon, 7 Feb 2011 14:01:13 +0200 (EET) Received-SPF: None (no SPF record) identity=mailfrom; client-ip=84.50.137.232; helo=[192.168.224.119]; envelope-from=margus@tione.eu; receiver=users@httpd.apache.org X-SMTP-Auth-NETI-Businessmail: no Message-ID: <4D4FDEF7.3000203@tione.eu> Date: Mon, 07 Feb 2011 14:00:55 +0200 From: =?UTF-8?B?TWFyZ3VzIFDDpHJ0?= User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101208 Thunderbird/3.1.7 MIME-Version: 1.0 To: users@httpd.apache.org References: <4D4EA158.1090405@tione.eu> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org Subject: Re: [users@httpd] SSL offload and load balancing with Apache2's mod_proxy and mod_balancer for Weblogic, Tomcat and Apache2 Hello! Thank you for your response! Glad to hear that I am not the only, who has thought that this solution would make life easier. Taking Apache-Event into use in our case is not an option, as Apache2-mpm-itk is used (proccesses running in different user rights) and new TCP connection has to be started for new client - it would be possible to assign different IP-s for different hosts, but named hosting is much easier to configure. If you would be so kind and take a look at the documentation also and give your oppinion: https://apache2-ssloffload-and-loadbalance.googlecode.com/svn/trunk/Documentation/apache2_ssloffload_and_loadbalance.pdf Page 3 contains summary - how it works - and most of it is automatic install + configuration by copy-paste to bash. On 02/07/2011 11:36 AM, Tom Evans wrote: > On Sun, Feb 6, 2011 at 1:25 PM, Margus Pärt wrote: >> Hello! >> >> >> I had an idea, how to SSL offload and Load balance with Apache2 a bit >> differently, and I implemented it also. >> >> Basically there 2 Apache instances running on the same machine with >> different configurations, one for SSL offload, other for balancing - client >> -> SSL offload -> Balancer -> backend server. >> >> >> If anyone would give feedback, just in form: "I like it" or "it's useless", >> I'd be glad. More detailed and constructive feedback would be even more >> appreciated. >> >> >> >> >> Project homepage and referrals to .pdf and .odf files are: >> https://code.google.com/p/apache2-ssloffload-and-loadbalance/ >> >> >> Best regards, >> Margus Pärt >> > I didn't read any of your docs, but this is effectively how we have > been hosting our websites for about the last 3-4 years. > > We have a pair of routers, which round-robin balances (with state) > each http requests onto one of a pair (or more, but currently a pair) > of boxes. These boxes all have the appropriate IPs of the hosted sites > assigned to their loopback (so that each machine can handle any > correctly routed request). > Each box has a pair of apache instances running on it, one running > apache-worker and doing SSL termination and proxying to the second > instance, running apache-event. The second instance serves all static > files, and proxys content from the application servers. > Each application is then split into a number of backends, and we use > mod_proxy_balancer on the proxies to manage which ones are active. > >> one 1Ghz proccessor was enough and it's load was between 4-12 > That's successful? If I look at graphs of our load average, it never > goes above 1. > > Cheers > > Tom > > --------------------------------------------------------------------- > The official User-To-User support forum of the Apache HTTP Server Project. > See for more info. > To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org > " from the digest: users-digest-unsubscribe@httpd.apache.org > For additional commands, e-mail: users-help@httpd.apache.org > --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See for more info. To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org " from the digest: users-digest-unsubscribe@httpd.apache.org For additional commands, e-mail: users-help@httpd.apache.org