After enabling mod_cache via the mod_mem_cache storage engine MIME types for html files revert to the DefaultType directive even if a force type directive has been placed in the http.conf file. The only file type I actually tested this on was a .css file in which the mime types file had a definition, there was an AddType declaration%, and a ForceType declaration on ALL CSS files. I had to improvise and disable caching on all files that this bug could interfere with. Note: Only tested on CSS files Only tested with the mod_mem_cache cache storage engine The original response with a clear cache was not documented so it is possible this is a bug with some sort of module that has impact on MIME types sent to the client
Created attachment 18097 [details] Patch against trunk
I can confirm this bug. Can you please check if the attached patch fixes your problem?
(In reply to comment #2) > I can confirm this bug. Can you please check if the attached patch fixes your > problem? I would like to, but if I am correct I can't just add that to the module seeing as it is already pre-compiled and I am on a Windows system. I appologize, but I don't have much proficiency with C/C++ programming. If you could give me the mod_mem_cache.so module for Windows with that patch applied I would be happy to give it a try.
Ok, scratch that. I downloaded the source and applied the patch to the proper section of the file, now the only problem is how exactly do I go about compiling the updated file?
You need to recompile the whole server, but you do not need to exchange anything more then the mod_mem_cache file within your installed server with the one that came out of your compilation. I am not a Windows guy so I cannot provide any help about how to compile httpd on Windows, but I guess the following links will provide valuable help: http://httpd.apache.org/docs/trunk/platform/win_compiling.html http://httpd.apache.org/docs/trunk/platform/windows.html
Hmmm... I just found this bug report. I'm going to give the attached patch a try and let you know what happens.
(In reply to comment #6) > Hmmm... I just found this bug report. I'm going to give the attached patch a try > and let you know what happens. After some limited testing this patch appears to fix the problem (applied it to apache-2.2.0)
(In reply to comment #7) > After some limited testing this patch appears to fix the problem (applied it to > apache-2.2.0) Also applied it to apache-2.2.2 and it appears to fix the problem in 2.2.2 as well.
Thanks for test. Committed to trunk as r399388 (http://svn.apache.org/viewcvs?rev=399388&view=rev).
*** Bug 39124 has been marked as a duplicate of this bug. ***
Proposed for backport to 2.2.x as r399856 (http://svn.apache.org/viewcvs?rev=399856&view=rev).
*** Bug 39539 has been marked as a duplicate of this bug. ***
Backported to 2.2.x as r410932 (http://svn.apache.org/viewvc?rev=410932&view=rev).