DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7778>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7778 mod_webapp does not set 'Content-Type: text/html' when reporting a compiler error Summary: mod_webapp does not set 'Content-Type: text/html' when reporting a compiler error Product: Tomcat 4 Version: 4.0.3 Final Platform: PC OS/Version: Linux Status: NEW Severity: Minor Priority: Other Component: Connector:Webapp AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] TC 4.0.3 & APACHE 1.3.20 since upgrading from TC4.0.1 -> TC4.0.3 the 500-Internal Server Error page which is displayed by TC when a compiler error occurs while serving a jsp-file no longer has it's content-type set to text/html. Probably many installations won't be affected by it, but since setting apache's defaulttype to something other than text/html is possible, TC should set the Content-Type to text/html explicitly. It was reproducible on TC4.0.2 final and TC4.0.3 final using the most recent mod_webapp.so (self-compiled and precompiled) with a simple jsp not closing the <%@ tag... I had TC4.0.1, TC4.0.2 and TC4.0.3 installed in parallel (all stock-installations downloaded and untarred from apache.org - not changed a single file)... tested this using the exact same config-file (with -config ....). I used a link to refer to the TC installation to be started. When running TC4.0.2 and TC4.0.3 every compilation-error had a MIME-Type of: text/plain. Running TC4.0.1 it was text/html again. Changing the DefaultType in apache's config from text/plain to text/html fixed the problem for now! However: it'd be nice to use a DefaultType of text/plain again (for some other reason...) Thanks :-) Matthias Ivers -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
