Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: neutral (athena.apache.org: 76.96.59.228 is neither permitted
 nor denied by domain of jim@jagunet.com)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1485\))
Subject: Re: [PATCH] mod_proxy Unix domain socket support
From: Jim Jagielski <jim@jaguNET.com>
In-Reply-To: <20120731200351.GB11038@gmail.com>
Date: Thu, 2 Aug 2012 10:07:32 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <F03FBBFA-49CB-4B94-B2D0-011F540139ED@jaguNET.com>
References: <20120731200351.GB11038@gmail.com>
To: dev@httpd.apache.org

Thx for the patch... I'll take a look.

On Jul 31, 2012, at 4:06 PM, Blaise Tarr <blaise.tarr@gmail.com> wrote:

> Hi,
>=20
> The attached patch adds support for Unix domain sockets (UDS) to
> mod_proxy. This is very beneficial when configuring a reverse proxy
> using mod_proxy_fcgi to connect to PHP-FPM. In some tests with ab
> there was over 20% improvement in the request rate when using a UDS
> instead of TCP.
>=20
> Since remote servers in mod_proxy are configured with a URL, I took
> the idea from this page on how to represent a UDS as a URL:
> http://daniel.haxx.se/blog/2008/04/14/http-over-unix-domain-sockets/
>=20
> So the host portion of the URL contains "socket=3D" followed by the =
URI
> encoded socket path (upper case characters must be encoded too). Below
> are a couple of examples where PHP-FPM's socket is /tmp/php-fpm.sock
> and the document root is /local/htdocs:
>=20
> ProxyPass fcgi://socket=3D%2ftmp%2fphp-fpm.sock/local/htdocs/
>=20
> RewriteRule (.*\.php) =
fcgi://socket=3D\%2ftmp\%2fphp-fpm.sock/local/htdocs/$1 [P,L]
>=20
> The following are not contained in the patch:
> * bump MMN due to mod_proxy.h changes
> * assign APLOGNO numbers
> * detection of AF_UNIX support in configure
>=20
> Thanks for your consideration,
> Blaise
> <proxy-uds.patch>