Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <dev@tomcat.apache.org>
Received-SPF: pass (athena.apache.org: local policy)
Message-ID: <47CF2703.8060305@ptc.com>
Date: Wed, 05 Mar 2008 17:04:35 -0600
From: Jess Holle <jessh@ptc.com>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
To: Tomcat Developers List <dev@tomcat.apache.org>
Subject: Re: Fix #43236
References: <7DD230BACBF7C14BB825154D431D2ED004C78692@posthausx.virtela.cc>
 <47CF243A.8090504@ptc.com>
In-Reply-To: <47CF243A.8090504@ptc.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

P.S. Thanks for the reply.  No one had responded yet and I despite much 
googling I really couldn't seem to find any discussion of the nuances of 
this area of the servlet spec.

Jess Holle wrote:
> Leech, Jonathan wrote:
>> I read the spec the same way as you do. I have written filters that 
>> are even more permissive than this fix, and
>> I have also written filters that strictly adhere to the spec. 
>> Strictly adhering to the spec is definitely the way to go.
>> If you want/need your application to violate the spec, you can write a
>> filter that allows it.
>>
>> I wasn't aware that you can call getOutputStream() in a JSP, when did
>> that change?
>>   
> I'm not 100% certain this works.  I am rather certain you can have a 
> JSP forward to something else that calls getOutputStream() -- 
> effectively on the same response.  I suspect the same sort of thing 
> would work in the page itself.
>
> Of course you have to be sure not to fill (and to reset) your 
> JspWriter's buffer in any case.
>
> -- 
> Jess Holle

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