tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 12107] New: - ContentType header value is set as null while using taglib/include directive
Date Tue, 27 Aug 2002 21:31:02 GMT
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=12107>.
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=12107

ContentType header value is set as null while using taglib/include directive

           Summary: ContentType header value is set as null while using
                    taglib/include directive
           Product: Tomcat 5
           Version: Unknown
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Major
          Priority: Other
         Component: Jasper2
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: prasad.subramanian@sun.com


If a JSP page has  an include directive or a taglib directive ,  then the
response header for ContentType  is set as null. It should be text/html"

This causes the XXML style comments and the HTML elemnst also to be displayed in
browsers like Netscape. 
However the display is perfect in IE.

Also having a page directive alone does not cause the header ContentType to be
set to null.To reproduce :
Write  a small JSP with a taglib directive 
Enable the requestdumpervalve in localhost to capture the headers.

--
To unsubscribe, e-mail:   <mailto:tomcat-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-dev-help@jakarta.apache.org>


Mime
View raw message