Re: Questions on the update to Apache 2.4

> On Nov 22, 2017, at 1:58 PM, Craig Treleaven wrote: > > Minor further questions…I’m a real neophyte at web servers so be gentle! > > It seems that mod_rewrite and mod_deflate are both commented out by default. > I believe they were both enabled in the prior version.

Re: Questions on the update to Apache 2.4

Craig, > On Nov 22, 2017, at 12:58 PM, Craig Treleaven wrote: > > Minor further questions…I’m a real neophyte at web servers so be gentle! > > It seems that mod_rewrite and mod_deflate are both commented out by default. > I believe they were both enabled in the prior

Re: Questions on the update to Apache 2.4

Minor further questions…I’m a real neophyte at web servers so be gentle! It seems that mod_rewrite and mod_deflate are both commented out by default. I believe they were both enabled in the prior version. Is there any particular reason for the change? Is it safe to use an httpd.conf file

Re: Questions on the update to Apache 2.4

William, That’s a valid point. apache2 supports platforms other than darwin/macOS, even though I wonder how many installations there are under FreeBSD and OpenBSD. I certainly don’t use MacPorts on my FreeBSD boxen. Under macOS there is no such thing as a /home or /usr/home directory. The

Re: Questions on the update to Apache 2.4

On Nov 13, 2017, at 5:55 PM, Marius Schamschula wrote: > >>> 2) In version 2.2 the httpd-userdir.conf file was customized to match >>> the /Users/*/Sites directory naming of macOS: was the corresponding >>> post-patch block in the Portfile forgotten or intentionally

Re: Questions on the update to Apache 2.4

Fixed in https://github.com/macports/macports-ports/commit/28289acb832ec0ca610a276ac70c2e4b4614ebe1 > On Nov 16, 2017, at 12:04 PM, Marius Schamschula > wrote: > > Davide, > > There is nothing in the Portfile that creates the original folder, so I > assume it is

Re: Questions on the update to Apache 2.4

Davide, There is nothing in the Portfile that creates the original folder, so I assume it is provided by make install. I’ll add a post-destroot script to delete it. > On Nov 16, 2017, at 11:40 AM, Davide Liessi > wrote: > >

Re: Questions on the update to Apache 2.4

Davide, I’ve had one more look. > On Nov 13, 2017, at 7:42 AM, Marius Schamschula wrote: > > Davide, > > >> On Nov 13, 2017, at 4:22 AM, Davide Liessi wrote: >> >> Hi. >> I have some questions regarding the apache2 port and the update to

Re: Questions on the update to Apache 2.4

Davide, > On Nov 13, 2017, at 10:14 AM, Davide Liessi wrote: > > 2017-11-13 14:42 GMT+01:00 Marius Schamschula : >>> 4) What is the purpose of having the original configuration files both >>> in ${prefix}/etc/apache2 with .orig suffix and in >>>

Re: Questions on the update to Apache 2.4

2017-11-13 14:42 GMT+01:00 Marius Schamschula : >> 4) What is the purpose of having the original configuration files both >> in ${prefix}/etc/apache2 with .orig suffix and in >> ${prefix}/etc/apache2/original? > > The original folder only has httpd.conf, but not

Re: Questions on the update to Apache 2.4

Davide, > On Nov 13, 2017, at 4:22 AM, Davide Liessi wrote: > > Hi. > I have some questions regarding the apache2 port and the update to version > 2.4. > > 1) The user:group changed from www:www in 2.2 to daemon:daemon in 2.4: > was the corresponding reinplace line

Questions on the update to Apache 2.4

Hi. I have some questions regarding the apache2 port and the update to version 2.4. 1) The user:group changed from www:www in 2.2 to daemon:daemon in 2.4: was the corresponding reinplace line in post-patch forgotten or intentionally omitted? 2) In version 2.2 the httpd-userdir.conf file was