apache installs its own copy of mime.types into /etc/apache2, but httpd.conf refers to /etc/mime.types, which belongs to app-misc/mime-types. Hmm? Reproducible: Always Steps to Reproduce:
I've tried and I can't seem to figure out where /etc/apache2/mime.types is coming from. It's not in our tarball, and our configuration points to /etc/mime.types. It could possibly be added by the `make install`, but I want to double check this before fixing the symptom (`rm ${D}/etc/apache2/mime.types`)
I'm also interested in the resolution of this, seeing as how there are some discrepencies between the two. Namely, the mime.types that is being installed by apache2 contains definitions for file extensions "htm" and "html", but /etc/mime.types lacks these. This can cause problems for less HTTP aware admins, as the lack of these definitions will cause a confusing scenario where IE will render a page with those extensions but Mozilla and Firefox won't. Whichever file file is decided on, it'd probably be a good idea to make sure that it includes these definitions. Considering the number of possible ebuilds that could be generating /etc/mime.types, I personally wouldn't be adverse to having Apache use its own mime.types file, but that obviously isn't up to me. :D halcyon apache2 # equery b mime.types [ Searching for file(s) mime.types in *... ] app-misc/mime-types-4 (/etc/mime.types) mail-client/pine-4.58 (/etc/mime.types) mail-client/mutt-1.5.8-r2 (/etc/mutt/mime.types) net-print/cups-1.1.20-r5 (/etc/cups/mime.types) net-www/apache-2.0.54-r31 (/etc/apache2/mime.types) net-zope/zope-2.7.4 (/usr/lib/zope-2.7.4/lib/python/OFS/mime.types) www-apps/horde-2.2.7 (/usr/share/webapps/horde/2.2.7/htdocs/scripts/mime_mapping/mime.types)
Errata: I meant "htm" and "xhtml", not "htm" and "html".
Packages are supposed to be trying to move to use the app-misc/mime-types package for mime.types. If there are mime.types that aren't in that file, please file a bug for that package. The extra/unused mime.types file in apache has now been removed.