  | Mailing List | | Home | | Forum Home | | JBoss - Java Application Server | | Tomcat - JSP/Servlet container | | Struts - A MVC web framework | | iText - An open source PDF Java Library | | JDOM - JDOM XML Parser | | J2EE - A mailing list for Java(tm) 2 Platform, Enterprise Edition | | J2EE Pattern - An interest list for Sun Java Center J2EE Pattern Catalog | | JSP - A mailing list about Java Server Pages specification and reference | | Servlet - A mailing list for discussion about Sun Microsystem's Java Servlet API Technology | |
Struts & Hibernate
|
|
|
  | | | Result of writing to response stream, and then setting response content type? | Result of writing to response stream, and then setting response content type? 2004-06-09 - By Karr, David
Back In a servlet 2.3 environment, what would be the effect of writing to the response outputstream (not necessarily flushing) and then setting the content type header of the response?
I had thought that would throw an IllegalStateException if the buffer had already been flushed by that point, but I can't find that in the specification.
What I do see is that it says the content type should be set first, but only if using a Writer. It doesn't appear to matter if you're using an OutputStream. I find it hard to believe it wouldn't matter for an OutputStream. Perhaps these comments in the spec only apply to the charset specification.
Will the result be that it simply ignores the new content type setting (if the buffer had been flushed)?
__ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ __ To unsubscribe, send email to listserv@(protected) and include in the body of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html Resources: http://java.sun.com/products/servlet/external-resources.html LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
|
|
 |