Mailing-List: contact users-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@httpd.apache.org
Received-SPF: pass (athena.apache.org: domain of tevans.uk@googlemail.com
 designates 209.85.216.45 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=googlemail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=DCUxMv+8rcWOKmkGxHCS0DEgyNR3GL9do0R3Rfc9bCO1ZU0gdzC6HevkZWc2WmlH8G
         +4kIJoGPPcMk0YIX+NrxZNoHlHk3hMfGCqT+uI/kGB3ZbK3byu5Nn5ND++q7RbUGQn1q
         4h6fvc0fhbuC5W7YIBs+ax9RyW9c/HihxInEY=
MIME-Version: 1.0
In-Reply-To: <4CD29148.6000907@gmail.com>
References: <4CD29148.6000907@gmail.com>
Date: Thu, 4 Nov 2010 17:01:58 +0000
Message-ID: <AANLkTinZHik3BfSwunCaJmAvL8hisGfv01xg4c2jNcSC@mail.gmail.com>
From: Tom Evans <tevans.uk@googlemail.com>
To: users@httpd.apache.org
Content-Type: text/plain; charset=UTF-8
Subject: Re: [users@httpd] SSL redirect ?

On Thu, Nov 4, 2010 at 10:56 AM, Brent Clark <brentgclarklist@gmail.com> wrote:
> Hiya
>
> I got an interesting request from a client and I was hoping to bounce this
> off you guys.
>
> ------------------------------------------------------------------------------------------------------------------------------------------------------------
> I need my linux server to accept incoming connections on port 8080 and
> forward them to an HTTPS address and do all communications.
>
> So, if a developer connects to, and uses
>
> https://abc.com/v4/transaction?wsdl
>
> it should redirect, communicate, and return data from
>
> https://trans.api.hidden.com/v4/transaction?wsdl
>
> Basically, I need to mask the trans.api.hidden.com and make all
> communications deal with abc.co.za.
>
> This is the same server.
>
> Personally I cant see this is possible, cause of the it been SSL. I would
> assume this activity as no different as a MITM attack.
> But googling, says I should look at mod_proxy. Is this possible?
>
> What do you guys think. If someone could help. It would be appreciated.
>
> Kind Regards
> Brent Clark
>

If your client connects to https://abc.com/ , then that is where SSL
will be terminated for the client. If you then proxy that connection
to https://trans.api.hidden.com/ , then that will be a separate SSL
connection between two apache servers, it will not carry any client
certificates that the client initially presented to https://abc.com .

wrt to your later question, apache is more than capable of proxying to
itself. I'm not sure you would need the overhead of an SSL connection
on a request that would never go on the wire.

Cheers

Tom

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> 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