Return-Path: Delivered-To: apmail-httpd-users-archive@www.apache.org Received: (qmail 97689 invoked from network); 24 Apr 2007 20:09:19 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 24 Apr 2007 20:09:19 -0000 Received: (qmail 89639 invoked by uid 500); 24 Apr 2007 20:09:15 -0000 Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 89622 invoked by uid 500); 24 Apr 2007 20:09:15 -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 89611 invoked by uid 99); 24 Apr 2007 20:09:15 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 Apr 2007 13:09:15 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of jslive@gmail.com designates 66.249.82.226 as permitted sender) Received: from [66.249.82.226] (HELO wx-out-0506.google.com) (66.249.82.226) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 Apr 2007 13:09:07 -0700 Received: by wx-out-0506.google.com with SMTP id t13so2231215wxc for ; Tue, 24 Apr 2007 13:08:47 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=hXHKtMvVbiWQh0yHP8HYHY49Z7FYWcEokMaIiVgWerbQKvm1HohSWt2RM8sDSU8+3iLU41WbrzSdhdfYgvZixjKzsfRukYBSzxqhZCBwpp9WuX5OyVfNWYhr1POANqXj5evZCOxtUGUP5aZ+AQZxT+SAFjg4x5MM0rYkLnls5ag= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=SJgU0iUTsUkajOK6VtZT5qrxX1OM3ty5pRz2tJt7PpvZKTqHUnvN55b6JCzx0hR1qH9sn7qMa+dZj5G6xfPI0tlbr5vlOFdrzrj8b4PgknfsWHse7ggcAKYKkGPgqw2M69Ex2ZVIGwuJRK0XTcABNnyqOckZ3KW8WR2jjCctvyk= Received: by 10.70.52.2 with SMTP id z2mr13084377wxz.1177445326971; Tue, 24 Apr 2007 13:08:46 -0700 (PDT) Received: by 10.100.200.13 with HTTP; Tue, 24 Apr 2007 13:08:46 -0700 (PDT) Message-ID: Date: Tue, 24 Apr 2007 16:08:46 -0400 From: "Joshua Slive" Sender: jslive@gmail.com To: users@httpd.apache.org In-Reply-To: <20070424134303.A42F210FB016@herse.apache.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20070424134303.A42F210FB016@herse.apache.org> X-Google-Sender-Auth: 6553e1ee5eb351bd X-Virus-Checked: Checked by ClamAV on apache.org Subject: Re: [users@httpd] SSL-enabled interaction with MySQL On 4/24/07, Naveen Rawat wrote: > 1. Primarily I wanted to know, if it is possible for an apache > (--enable-mods-shared=all --enable-ssl=shared --enable-so) module to > interact with a SSL-enabled MySQL (--with-openssl=)? > > 2. If yes, then considering that I have got required keys/certificates for > both the client, server and the CA, what are the apache-end APIs that would > be needed to make this SSL session possible? You have not told us anything about how exactly you want apache and mysql to interact. Most often, database interaction is the responsibility of a web app sitting on top of apache (php, etc). Joshua. --------------------------------------------------------------------- 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