From: Wolfgang Apolinarski <wolfgang@apolinarski.de>
To: development@lists.ipfire.org
Subject: Upgrade to Apache 2.4
Date: Fri, 14 Apr 2017 16:25:05 +0200 [thread overview]
Message-ID: <000401d2b52a$e9579250$bc06b6f0$@apolinarski.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 799 bytes --]
Hi everyone,
I created an upgrade to Apache 2.4:
https://github.com/wapolinar/ipfire-2.x/tree/apache_24
It should be up-to-date with the current next branch, but I could rebase/merge it with whatever branch you want me to.
I also had to update some configuration files of addons, because they did not comply to the Apache 2.4 syntax. Please have a look at
this changes as well, I tested them on my virtual IPFire machine and as far as I could see it they are working, but there might be
some problems.
I'm willing to change the apache configuration of other addons/configuration files, if necessary.
If you think that IPFire does not need this update, this is also ok to me, I started creating it, after the discussion about the
htpasswd-tool started.
Best regards,
Wolfgang
next reply other threads:[~2017-04-14 14:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-14 14:25 Wolfgang Apolinarski [this message]
2017-04-16 16:12 ` Michael Tremer
2017-04-16 21:13 ` AW: " Wolfgang Apolinarski
2017-04-18 12:05 ` Michael Tremer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='000401d2b52a$e9579250$bc06b6f0$@apolinarski.de' \
--to=wolfgang@apolinarski.de \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox