You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tapestry.apache.org by bu...@apache.org on 2004/04/14 18:53:56 UTC

DO NOT REPLY [Bug 27703] - ResponseOutputStream.setHeader() & ResponseOutputStream.setContentType() problems

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=27703>.
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=27703

ResponseOutputStream.setHeader() & ResponseOutputStream.setContentType() problems

hlship@apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID



------- Additional Comments From hlship@apache.org  2004-04-14 16:53 -------
Until you can provide details of your environment, this will have to stay 
invalid. The behavior you are seeing is consistent with a flawed servlet 
container, not a problem with Tapestry. Alternately, you might have a Servlet 
filter in place that is responsible for this problem.

Obviously, those using leading containers such as Tomcat, Jetty, WebLogic and 
WebSphere have not seen this problem.

---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org