Return-Path: X-Original-To: apmail-httpd-users-archive@www.apache.org Delivered-To: apmail-httpd-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 22DB910BE6 for ; Tue, 4 Feb 2014 20:05:11 +0000 (UTC) Received: (qmail 46419 invoked by uid 500); 4 Feb 2014 20:04:45 -0000 Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 45913 invoked by uid 500); 4 Feb 2014 20:04:27 -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 45666 invoked by uid 99); 4 Feb 2014 20:04:12 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Feb 2014 20:04:12 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,WEIRD_PORT X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of yehuda@ymkatz.net designates 209.85.213.182 as permitted sender) Received: from [209.85.213.182] (HELO mail-ig0-f182.google.com) (209.85.213.182) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Feb 2014 20:04:08 +0000 Received: by mail-ig0-f182.google.com with SMTP id uy17so9380426igb.3 for ; Tue, 04 Feb 2014 12:03:47 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:dkim-signature:mime-version:in-reply-to :references:from:date:message-id:subject:to:content-type; bh=BfctXE0Y0VXlPHkGOxNjBMOTJTQGB/s+h1F15S3JH9s=; b=cIFchIXDHpEcKvVYQAeGtKVHxCbtXfC8c6Gpy/eUr3232UetJhL/wbs/FOZhV7HNRv BIP08Kq5anma5VqLhwRWvco55k8uUdlyd1AzeScfBtN/E5kRs+ry6XL1q4ie4pa7jjvW FZaYMqGtwzHMQmQFIYzchnlMF6EY9LChVTOH2201xNpWNRPvpCm+kkl4RA0GpZyPlNN7 BaPRLDGqUVwos2r9+biuytVzogMij5t7k0uQ2Ie25nJ1epgqGnOq6RhWR1XwgatZgFMd 0nozkfRU802bHR9ErTpUGqTWJBPPAdZdFygsJDaqaYuENWorFNhLT40lihMMw8vXp8il vSyA== X-Gm-Message-State: ALoCoQkeaiQ7SqvNSJMiypLlwBsU1i8eVVLRBDDi4puhUr4X/qxuhC4IfWMoOMqL8eS+RcO9Mrzb X-Received: by 10.50.65.106 with SMTP id w10mr12680038igs.13.1391544227337; Tue, 04 Feb 2014 12:03:47 -0800 (PST) Received: from mail-ig0-x231.google.com (mail-ig0-x231.google.com [2607:f8b0:4001:c05::231]) by mx.google.com with ESMTPSA id f2sm42410653igt.6.2014.02.04.12.03.46 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 04 Feb 2014 12:03:46 -0800 (PST) Received: by mail-ig0-f177.google.com with SMTP id k19so9344333igc.4 for ; Tue, 04 Feb 2014 12:03:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ymkatz.net; s=g; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=BfctXE0Y0VXlPHkGOxNjBMOTJTQGB/s+h1F15S3JH9s=; b=cqK9iBLflblbR2hMLQ5+Ik7l+KAcQJPDJZ7bIA8GRKna1pZJG7mVGAg7KKaRgZdtpJ HBQLYWuEKSPrD982XJmlsM0OMmiHBBDMuFgficYxc5KhL0KYTbLPwoYGxMb6OOTDskLX nDX/SPX3O40/FjIXRSbUuUlabpVkaWH1wUgjY= X-Received: by 10.50.114.168 with SMTP id jh8mr18951227igb.6.1391544226161; Tue, 04 Feb 2014 12:03:46 -0800 (PST) MIME-Version: 1.0 Received: by 10.43.16.138 with HTTP; Tue, 4 Feb 2014 12:03:26 -0800 (PST) In-Reply-To: References: From: Yehuda Katz Date: Tue, 4 Feb 2014 15:03:26 -0500 Message-ID: To: "users@httpd.apache.org" Content-Type: multipart/alternative; boundary=089e01229f864a2d2004f19a23e3 X-Virus-Checked: Checked by ClamAV on apache.org Subject: Re: [users@httpd] Traffic forwarding..... --089e01229f864a2d2004f19a23e3 Content-Type: text/plain; charset=ISO-8859-1 On Tue, Feb 4, 2014 at 1:37 PM, Charles W Buege wrote: > Here's what I'd like to do now: If there is an incoming connection to > www.avengers.org that is going to port 3306 (MySQL) for example, how can > I configure the system to pass this information along? > Services like MySQL don't have the idea of virtual hosting. All they know is that a connection was made. I am pretty sure that virtual hosting was only added to HTTP in version 1.1 with the addition of the Host header. I use SSH port forwarding to connect to MySQL, which may help with what you are trying to do. ssh -L local_port:remote_host:remote_port ssh_server So for example: ssh -L 3306:site2.avengers.org:3306 10.1.12.11 ssh -L 3306:www.avengers.org:3306 10.1.12.11 and then connect your MySQL client to localhost:3306. - Y --089e01229f864a2d2004f19a23e3 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On T= ue, Feb 4, 2014 at 1:37 PM, Charles W Buege <cbuege@moreycorp.com= > wrote:
Here's what I'd like to = do now: =A0If there is an incoming connection to www.avengers.= org that is going to port 3306 (MySQL) for example, how can I configure the system to pass this information along?

Services like MySQL don't have the idea of virtual hosting. All = they know is that a connection was made.
I am pretty sure that vi= rtual hosting was only added to HTTP in version 1.1 with the addition of th= e Host header.

I use SSH port forwarding to connect to MySQL, which ma= y help with what you are trying to do.

ssh -L local_port:remote_host:remote_port ssh_server
So for= example:

=
ssh -L 3306:site2.avengers.org:3306 10.1.12.11<=
br>
ssh -L 3306:www.avengers.org:33=
06 10.1.12.11
and then connect your MySQL client to localh= ost:3306.

- Y
--089e01229f864a2d2004f19a23e3--