Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#18503 - [apache] Change default apache configuration to be less heavy
Attached to Project:
Arch Linux
Opened by Mark (markg85) - Sunday, 28 February 2010, 19:41 GMT
Last edited by Jan de Groot (JGC) - Monday, 01 March 2010, 15:46 GMT
Opened by Mark (markg85) - Sunday, 28 February 2010, 19:41 GMT
Last edited by Jan de Groot (JGC) - Monday, 01 March 2010, 15:46 GMT
|
DetailsHi,
After installing apache and diving in the httpd.conf file i noticed the enormous list of apache modules that is loaded by default! Lets first take a note of the likely assumptions that someone wants to do with a apache on archlinux. - The user PROBABLY wants to just have apache for local development reasons - The user PROBABLY wants to install PHP - And nice url's (mod_rewrite) is something we can't live without anymore these days So, why not "tune" the apache configuration to do exactly that? O and even more funny. mod_rewrite is in fact installed and enabled by default BUT rewriting itself is off since AllowOverride is set to None instead of All. I propose to use this config: http://codepad.org/BTT3Sc9R I disabled nearly all modules including SSL since that sucks up requests and is, in my opinion, not likely to be the first thing a arch user is going to use when he installs apache. The other edit i did in this was AllowOverride All in the <Directory "/srv/http"> dir. Note that using this config does make it a closer match to the clean lighttpd config! I don't know if those disabled modules should remain in the file as commented or just removed completely from the conf..? That's up to the maintainer to decide i guess. So, what do you think of this suggestion? Regards, Mark |
This task depends upon
Comment by Jan de Groot (JGC) -
Monday, 01 March 2010, 15:45 GMT
We ship as much as possible vanilla configuration files. Making assumptions on configuration is wrong here. Not everyone installs PHP, so enabling PHP in the default configuration is plain wrong. Not everyone uses apache for development, and adding AllowOverride All is insecure by default. Upstream has made choices for the default configuration, we're just following them as much as possible.