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 B2DEBDFF0 for ; Mon, 26 Nov 2012 04:40:39 +0000 (UTC) Received: (qmail 12081 invoked by uid 500); 26 Nov 2012 04:40:36 -0000 Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 12037 invoked by uid 500); 26 Nov 2012 04:40:35 -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 11984 invoked by uid 99); 26 Nov 2012 04:40:32 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 26 Nov 2012 04:40:32 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,NORMAL_HTTP_TO_IP,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of kev.castellow@gmail.com designates 74.125.82.173 as permitted sender) Received: from [74.125.82.173] (HELO mail-we0-f173.google.com) (74.125.82.173) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 26 Nov 2012 04:40:26 +0000 Received: by mail-we0-f173.google.com with SMTP id z2so2568866wey.18 for ; Sun, 25 Nov 2012 20:40:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=Iwfvx4XRjhnG+lDK1gBj0r1aJy5EuErv8lrBp9E8U+E=; b=KBiAobS5F9XcCwQIfr7eN1fdCv8+I4WQd9LPvlrnEtCvSg4DyXsSbxz7FqDdJMwc5o tl+yL8KZAQkaQfnOmSMsNWJDeHQeetitzMJNl31UHLnC5raQWOE+nO+wLWGtpicLkWKZ 91cxMmruRVyy8HxrrLlTWOOau9SQdEb5UxK3gNkQgTOXn2lTCY2GOs/V1VsM2Q4RffQE Iw/UQhnpYd+WjGmdxGSaSIIcUfOBvftrUMCRlHJ4ODS9TFjX2ZDOjFmiDw0VVNeMWTI6 9okGEPV4xr2lLLIxkLMJ6v1DjYF7HWUw5uQIO+WZwjF57PTJGW8d8MGbD7M/ZYKGVjyk 5CrA== MIME-Version: 1.0 Received: by 10.216.93.137 with SMTP id l9mr3122762wef.132.1353904806380; Sun, 25 Nov 2012 20:40:06 -0800 (PST) Received: by 10.194.37.132 with HTTP; Sun, 25 Nov 2012 20:40:06 -0800 (PST) In-Reply-To: <5D55C6CD-D202-4C69-9785-268ABBBA32BA@electrichendrix.com> References: <5D55C6CD-D202-4C69-9785-268ABBBA32BA@electrichendrix.com> Date: Sun, 25 Nov 2012 23:40:06 -0500 Message-ID: From: Kevin Castellow To: users@httpd.apache.org Content-Type: multipart/alternative; boundary=0016e6d99af70b446204cf5e874e X-Virus-Checked: Checked by ClamAV on apache.org Subject: Re: [users@httpd] Interesting Problem --0016e6d99af70b446204cf5e874e Content-Type: text/plain; charset=ISO-8859-1 I would start with this page: http://httpd.apache.org/docs/2.2/mod/mod_proxy.html There are great examples there. Determine the match that you want. Then set up the destination to the right ip and port. It sounds like you had a match but maybe the destination was not what you wanted. Work by modifying one setting at a time. Kevin On Sun, Nov 25, 2012 at 11:00 PM, Chris Arnold wrote: > On Nov 25, 2012, at 10:17 PM, Kevin Castellow > wrote: > > Yes. That is exactly what a proxy would do for you. > Turn on logging to know for sure. > > Ok, I disabled the last proxy pass entry to the all vhost and now I do not > get the webmail login. What I was trying to do with the proxy pass entry > was proxy all https://mail.domain.com traffic to the email server. The > commented out proxy pass looks like: > Proxypass / https://192.168.124.3/ > Proxypassreverse / https://192.168.124.3/ > > How do I go about proxying https://mail.domain.com traffic to the email > server? > > > On Sun, Nov 25, 2012 at 10:14 PM, Chris Arnold < > carnold@electrichendrix.com> wrote: > >> We have a problem and I am trying to either confirm or deny it being an >> apache config mistake. 2 servers, 1 is 192.168.123.3 and 1 is >> 192.168.124.3. On the 192.168.124.3 server we have email; on the >> 192.168.123.3 server we have web server. When I go to >> https://192.168.123.3 I am presented with the webmail login. This should >> not be as the email is on 192.168.124.3. The 192.168.123.3 server is doing >> proxy pass. Could apache be redirecting this traffic to 192.168.124.3 and >> keeping the 192.168.123.3 address in the address bar? >> >> Sent from my iPhone >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org >> For additional commands, e-mail: users-help@httpd.apache.org >> >> > --0016e6d99af70b446204cf5e874e Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I would start with this page:
http://httpd.apache.org/docs/2.2/mod/mod_proxy.html=A0=A0=A0=A0=A0=A0 There are great examples there.

Determine the m= atch that you want.=A0 Then set up the destination to the right ip and port= .=A0=A0 It sounds like you had a match but maybe the destination was not wh= at you wanted.=A0 Work by modifying one setting at a time.

Kevin

On Sun, Nov 25, 2012 at 11:00 P= M, Chris Arnold <carnold@electrichendrix.com> wrot= e:
On = Nov 25, 2012, at 10:17 PM, Kevin Castellow <kev.castellow@gmail.com> wrote:

Yes.=A0 That is exactly what = a proxy would do for you.=A0
Turn on logging to know for sure.

=
Ok, I disabled the last proxy pass entry to the al= l vhost and now I do not get the webmail login. What I was trying to do wit= h the proxy pass entry was proxy all https://mail.domain.com traffic to the email server. Th= e commented out proxy pass looks like:
Proxypassreverse / https://192.168.124.3/

How do I go about proxying https://mail.domain.com traffic to the email server?


On Sun, N= ov 25, 2012 at 10:14 PM, Chris Arnold <carnold@electrichendrix.c= om> wrote:
We have a problem and I am trying to either = confirm or deny it being an apache config mistake. 2 servers, 1 is 192.168.= 123.3 and 1 is 192.168.124.3. On the 192.168.124.3 server we have email; on= the 192.168.123.3 server we have web server. When I go to https://192.168.123.3 I am presente= d with the webmail login. This should not be as the email is on 192.168.124= .3. The 192.168.123.3 server is doing proxy pass. Could apache be redirecti= ng this traffic to 192.168.124.3 and keeping the 192.168.123.3 address in t= he address bar?

Sent from my iPhone
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org



--0016e6d99af70b446204cf5e874e--