The mime-mapping of conf/web.xml in Tomcat 7 ist far more complete than in Tomcat 6 [1]. Please keep both sections synchronized. It's quite a tedious work to create a suitable patch with every release and apply that to Tomcat 6. [1] svn diff http://svn.apache.org/repos/asf/tomcat/tc6.0.x/trunk/conf/web.xml http://svn.apache.org/repos/asf/tomcat/tc7.0.x/trunk/conf/web.xml
AFAIK, Nothing is broken with the current list of mime-mappings in Tomcat 6, so I am marking this as enhancement. Several notes 1. web.xml in Tomcat 7 is 100 kilobytes larger than the one in Tomcat 6. I wouldn't be wondered if the time to parse those additional 3000 lines and the memory used to store the mappings for each deployed application were noticeable in some configurations. 2. There is nothing wrong with having your own copy of web.xml to replace the one provided by Tomcat. I would not expect many changes to the default web.xml in Tomcat 6, so you do not need to update your copy. 3. Tomcat 6 is RTC, so someone has to prepare the actual patch to be proposed for a vote. Personally, I think it is too late to backport such enhancement to Tomcat 6. Though if anyone else goes with it, I wouldn't mind. Maybe ask on opinions on dev@. Are there any more requests for this?
(In reply to comment #1) > AFAIK, Nothing is broken with the current list of mime-mappings in Tomcat 6, > so I am marking this as enhancement. Sorry, I did not mind to file a bug actually. This is a enhancement of course. > Several notes > > 1. web.xml in Tomcat 7 is 100 kilobytes larger than the one in Tomcat 6. > > I wouldn't be wondered if the time to parse those additional 3000 lines and > the memory used to store the mappings for each deployed application were > noticeable in some configurations. This happens anyway if you run an app with Tomcat 7. Why this should make a difference to Tomcat 6? > 2. There is nothing wrong with having your own copy of web.xml to replace > the one provided by Tomcat. I know, I have done this partially. But it has a huge drawback. Everyone has to do the same stupid work over and over again, patch, check, patch, etc. We can do this in a single place, here. > I would not expect many changes to the default web.xml in Tomcat 6, so you > do not need to update your copy. > > 3. Tomcat 6 is RTC, so someone has to prepare the actual patch to be > proposed for a vote. > > > Personally, I think it is too late to backport such enhancement to Tomcat 6. > Though if anyone else goes with it, I wouldn't mind. Maybe ask on opinions > on dev@. What is RTC? Yes, I will raise this on dev@ as you advise. Спасибо Костя!
Created attachment 29952 [details] Patch against Tomcat 6.0 trunk
The proposed patch creates duplicate definitions for: htke, odft, oti, svc, svd, text, tfi, tfm, tga, thmx, s, s3m, saf, sbml, sc, scd, scm, scq, scs, scurl, sda, sdc, sdd, sdkd, sdkm, sdp, sdw, see, seed, sema, semd, semf, ser, setpay, setreg, sfd-hdstx, sfs, sfx, sgi, sgl, sgm, sgml I'll have an updated proposal shortly.
Created attachment 29962 [details] Proposed patch New patch that doesn't create the duplicates.
Updated patch proposed for 6.0.x.
Fixed in 6.0 by r1476538 , will be in 6.0.37.