DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=28423>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=28423 jsp page directive doesn't work [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID ------- Additional Comments From [EMAIL PROTECTED] 2004-07-18 22:14 ------- This is caused by a charset element being added to the content-type string. Unfortunately the JSP spec (as clarified by the errata) requires this. The work-around doesn't work because of a previous call to setContentType() that includes a charset element (again as required by the spec). Although other web containers may work, tomcat is correctly implementing the JSP specification. NB Tomcat 5 has the same behaviour. One possible work-around is to use a servlet where you have control over calls to setContentType(). --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
