You are not logged in.
Any idea why /etc/httpd/conf/mime.types is not backed up on apache upgrade?
From https://wiki.archlinux.org/index.php/LAMP
Add this line in /etc/httpd/conf/mime.types:
application/x-httpd-php php php5
AFAICS, it should be backed up or not modified at all.
Offline
See the backup array: https://projects.archlinux.org/svntogit … ges/apache
backup=(etc/httpd/conf/httpd.conf
etc/httpd/conf/extra/httpd-{autoindex,dav,default,info,languages}.conf
etc/httpd/conf/extra/httpd-{manual,mpm,multilang-errordoc}.conf
etc/httpd/conf/extra/httpd-{ssl,userdir,vhosts}.conf
etc/conf.d/apache
etc/logrotate.d/httpd)If you modify these files a .pacsave file will get created instead of them being just overwritten. /etc/httpd/conf/mime.types is provided by the apache package, so any changes you do to this file will be lost on update.
I know nothing about apache and I have no idea what is the correct course of action here. If you think this file shouldn't be provided by the package or that it should not be overwritten, open a bug report.
Offline
FYI /etc/httpd/conf/mime.types has been added to backup() in the latest 2.4.7 release. This release is in [testing].
And BTW there is a good chance to try the package and give a feedback before it became official.
Read it before posting http://www.catb.org/esr/faqs/smart-questions.html
Ruby gems repository done right https://bbs.archlinux.org/viewtopic.php?id=182729
Fast initramfs generator with security in mind https://wiki.archlinux.org/index.php/Booster
Offline
Thanks for the responses. I decided to leave mime.types alone and add new types in httpd.conf. BTW, this method is recommended in the apache docs :
It is recommended that new MIME types be added using the AddType directive rather than changing the TypesConfig file.
You should not edit the mime.types file, because it may be replaced when you upgrade your server.
Offline