On Feb 25, 2014, at 7:26 AM, Yann Ylavic <[email protected]> wrote:
> On Mon, Feb 24, 2014 at 9:41 PM, Jim Jagielski <[email protected]> wrote: >> >> On Feb 24, 2014, at 10:05 AM, Yann Ylavic <[email protected]> wrote: >> >>> I use the following config : >>> >>> <VirtualHost 127.0.0.1:60080> >>> ServerName localhost:60080 >>> >>> RewriteEngine on >>> RewriteRule "^/(.*)$" "unix:/tmp/backend.sock|http://localhost/$1"; [P,NE] >>> >>> <Proxy "unix:/tmp/backend.sock|http://localhost"; disablereuse=off> >>> </Proxy> >>> </VirtualHost> >>> >> >> Why the <Proxy> container? What is that designed to do >> or what is it there for? I'm pretty sure that's the >> issue. >> >> You are just trying to Proxy all requests to the socket at >> /tmp/backend.sock, right? >> > > Right, but this config has no other purpose than testing that one can > use a RewriteRule and a <Proxy> declaration for UDS backend > connections to be reusable (this one is with the http scheme, but it > could be fcgi or any other proxy scheme...), so that I can give my +1 > to STATUS ;) > > Should this simply work? > The use of the UDS path in <Proxy> statements is not supported; I never anticipated the need for it.. It's a ProxyPass and/or BalancerMember "enhancement" (ie: anything that defines a "worker" instead of a "path").
