Mailing-List: contact modules-dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: modules-dev@httpd.apache.org
Received-SPF: pass (nike.apache.org: domain of info@bnoordhuis.nl designates
 74.125.83.45 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAKtCLL6_PVBuKC3VwO=eVJPOWj9Uabi-uDPHzBb_+uveXqdOcA@mail.gmail.com>
References: 
 <CAKtCLL6_PVBuKC3VwO=eVJPOWj9Uabi-uDPHzBb_+uveXqdOcA@mail.gmail.com>
Date: Thu, 7 Jul 2011 23:18:22 +0200
Message-ID: 
 <CAHQurc90XdWrpL=7j1K0SDMtQg-3+unCGDPfFNA4APTp4ohpNA@mail.gmail.com>
Subject: Re: proxying another protocol to http/https
From: Ben Noordhuis <info@bnoordhuis.nl>
To: modules-dev@httpd.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Thu, Jul 7, 2011 at 02:56, Jodi Bosa <jodibosa@gmail.com> wrote:
> I would like to leverage mod_proxy and mod_proxy_http to proxy client
> requests (from another protocol).
> Assuming I have input & output filters that handle the other protocol wit=
h
> the client, shouldn't I simply be able to:
>
>
> Handler
> {
> =A0 =A0r->filename =3D apr_psprintf(r->pool, "proxy:https://%s", hostname=
);
> =A0 =A0r->proxyreq =3D PROXYREQ_PROXY;
> =A0 =A0return DECLINED; /* to allow mod_proxy to kick in and do it's thin=
g */
> }

That should work if your handler runs before mod_proxy. Hook it at
APR_HOOK_REALLY_FIRST.