Mailing-List: contact users-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@httpd.apache.org
MIME-Version: 1.0
From: Daniel Frank <danthehitman@gmail.com>
Date: Mon, 27 Feb 2017 16:16:48 -0700
Message-ID: <CAFaNjB=p_Ei_hW-Lc3TN=AFe9KygXTU-gYAsA48VBQnupKrr+Q@mail.gmail.com>
To: users@httpd.apache.org
Content-Type: multipart/alternative; boundary=001a1149097a1776f805498b4621
Subject: [users@httpd] Forward Proxy on behalf of the client instead of as a tunnel
archived-at: Mon, 27 Feb 2017 23:16:59 -0000

--001a1149097a1776f805498b4621
Content-Type: text/plain; charset=UTF-8

All,

I am trying to set Apache up as a forward proxy to help solve an issue that
we have where an HTTP Client in our application does not support TLS 1.2
but an API that we need to consume only supports TLS 1.2.  What I am
attempting to do is use Apache to talk HTTPS/TLS 1.2 to the target API but
allow my internal client to talk to the proxy over HTTP.

I had it in my head that this was what a forward proxy was going to give me
so after having set up a forward proxy and configuring my application to
use it I was surprised to see that I was getting exactly the same behavior
that I was getting when I had no proxy configured (failure of my internal
client to speak TLS 1.2).

So my question is; can Apache be configured as a FORWARD proxy to speak
HTTP with the caller but HTTPS to the callee?

I have spent a lot of time searching and I did check the mailing list
archives but it's entirely possible that I just dont even know what to
search for to get a good answer so if this is a dumb question I sincerely
apologize for wasting the groups time.

Thanks in advance for any help.

-Dan

--001a1149097a1776f805498b4621
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><span style=3D"font-size:12.8px">All,</span><div style=3D"=
font-size:12.8px"><br></div><div style=3D"font-size:12.8px">I am trying to =
set Apache up as a forward proxy to help solve an issue that we have where =
an HTTP Client in our application does not support TLS 1.2 but an API that =
we need to consume only supports TLS 1.2.=C2=A0 What I am attempting to do =
is use Apache to talk HTTPS/TLS 1.2 to the target API but allow my internal=
 client to talk to the proxy over HTTP.</div><div style=3D"font-size:12.8px=
"><br></div><div style=3D"font-size:12.8px">I had it in my head that this w=
as what a forward proxy was going to give me so after having set up a forwa=
rd proxy and configuring my application to use it I was surprised to see th=
at I was getting exactly the same behavior that I was getting when I had no=
 proxy configured (failure of my internal client to speak TLS 1.2).</div><d=
iv style=3D"font-size:12.8px"><br></div><div style=3D"font-size:12.8px">So =
my question is; can Apache be configured as a FORWARD proxy to speak HTTP w=
ith the caller but HTTPS to the callee?</div><div style=3D"font-size:12.8px=
"><br></div><div style=3D"font-size:12.8px">I have spent a lot of time sear=
ching and I did check the mailing list archives but it&#39;s entirely possi=
ble that I just dont even know what to search for to get a good answer so i=
f this is a dumb question I sincerely apologize for wasting the groups time=
.</div><div style=3D"font-size:12.8px"><br></div><div style=3D"font-size:12=
.8px">Thanks in advance for any help.</div><div style=3D"font-size:12.8px">=
<br></div><div style=3D"font-size:12.8px">-Dan</div></div>

--001a1149097a1776f805498b4621--