Re: Listen on UDS
I'd been musing, coincidentally, about being able to run httpd as a FastCGI. The motivation for this is a packaged webapp - Wordpress, say - that includes .htaccess files in the deployed package. Having the genuine Apache httpd able to serve the application and apply .htaccess restrictions would be a boon, even if the daemon listening on port 443 is different. -- Tim Bannister – [email protected]
Re: Listen on UDS
That's what I thought too, but I didn't want to assume :) Let me look at what would be involved. > On Apr 28, 2015, at 3:19 PM, Jim Riggs wrote: > >> On 28 Apr 2015, at 10:20, Graham Leggett wrote: >> >> On 28 Apr 2015, at 5:17 PM, Jim Jagielski wrote: >> >>> Anyone looked into having httpd be able to Listen on a UDS, as >>> well as scenarios where we may want that even? >> >> I have always wanted it - one thing it allows us to do is reverse proxy to >> versions of httpd (or other daemon software) running as another user, with a >> proper hope of securing it. > > +1. Reverse proxy is the prime example I can think of for it. >
Re: Listen on UDS
> On 28 Apr 2015, at 10:20, Graham Leggett wrote: > > On 28 Apr 2015, at 5:17 PM, Jim Jagielski wrote: > >> Anyone looked into having httpd be able to Listen on a UDS, as >> well as scenarios where we may want that even? > > I have always wanted it - one thing it allows us to do is reverse proxy to > versions of httpd (or other daemon software) running as another user, with a > proper hope of securing it. +1. Reverse proxy is the prime example I can think of for it.
Re: Listen on UDS
On 28 Apr 2015, at 5:17 PM, Jim Jagielski wrote: > Anyone looked into having httpd be able to Listen on a UDS, as > well as scenarios where we may want that even? I have always wanted it - one thing it allows us to do is reverse proxy to versions of httpd (or other daemon software) running as another user, with a proper hope of securing it. Regards, Graham —
