Many app servers buffer the response output and allow anything to be done
to the response until the first time the buffer is flushed to the
client. This can lead to runtime situations where you can call
response.setHeader() AFTER writing something to the response... so long as
you don't write enough to cause the buffer to flush.
Needless to say, this "feature" can lead to some pretty annoying debugging
sessions and bewildered people when their application works in something
loose (like WL and, apparently, Resin), but not in Tomcat. I'm especially
authoritative on that last point. ;)
justin
At 03:38 PM 9/6/2002, you wrote:
>Because this:
><%
>response.setHeader("Cache-Control","no-cache");
>response.setHeader("Pragma","no-cache");
>
>will commit the response, after which you cannot redirect.
>
>Not sure why Resin would allow this.
>
>
>
>-----Original Message-----
>From: Dionisio Ruiz de Zarate [mailto:[EMAIL PROTECTED]]
>Sent: Friday, September 06, 2002 5:28 PM
>To: [EMAIL PROTECTED]
>Subject: Error in tomcat but not in resin (caucho)
>
>
>Why bellow code is error in tomcat?
>this code runs well in resin.
>there is any error?
>thanks
>
>code:
>
>
><%
>response.setHeader("Cache-Control","no-cache");
>response.setHeader("Pragma","no-cache");
>
>--
>To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
>For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
