On 12 Jun 2008, at 22:51, Gunnar Wolf wrote: > Alvaro Lopez Ortega dijo [Thu, Jun 12, 2008 at 07:11:08AM +0200]: >> It will change the rules structure, but it will not add the default >> mime types. You can simply copy and paste them from / >> cherokee.conf.sample in the source directory. > > Álvaro, BTW... Why not trust in the systemwide MIME types? Why did you > feel it's better to include them in the Cherokee configuration? Most > Unixy systems have a /etc/mime.types or similar, and a basic fallback > one could be shipped just for lesser systems...
The keys here are 'most' and 'similar'. We cannot relay on something that most of the Unix system have, or that is similar among them. It would be a mess. Besides, when we used the global mime.type we hit a couple of important issues. For instance, we could not define "Max-Age" custom values for its entries. So if we wanted to support the feature, cherokee-admin would have to keep another internal list of mime types to custom max-age values (which could get out or sync eventually). The idea is to keep the task of administrating a Cherokee server as simple as possible; that is what cherokee-admin is for. So, I do agree with you about the global mime.types file: it would be good to use it, although due a number of issues I don't think it is possible neither to integrate it well with cherokee-admin, nor to use it in the way we would need. There is something that might help though. When the user adds a new Mime entry, Cherokee-admin could read the system mime.types (if present) and show the entries in the system file that are not configured in cherokee so the user could pick from a list instead or writing the mime type. It's not the perfect solution, but it is a step closer. -- Greetings, alo. http://www.alobbs.com/ _______________________________________________ Cherokee mailing list [email protected] http://cherokee-project.com/cgi-bin/mailman/listinfo/cherokee
