Markus Schönhaber wrote: > Mark Thomas wrote:
>> That said I wouldn't be against a patch that introduced a >> useFileEncodingInCharset parameter (although a shorter name would be better >> ;) > > Great! I'll dig into DefaultServlet's source and see what I can come up > with. OK, I think I have, by and large, understood how the DefaultServlet works and added code to append the charset info (if wanted and applicable) to the Content-Type response header. What I ended up with is the same as if I had simply searched the code for all places where Content-Type is set and add my code there. Seems reassuring to me. I'll do some more testing and then attach the patch to https://issues.apache.org/bugzilla/show_bug.cgi?id=41773 Are there any (non-obvious) testcases that you think deserve special attention? Regards mks --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
