Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (athena.apache.org: local policy)
From: "Caldarale, Charles R" <Chuck.Caldarale@unisys.com>
To: Tomcat Users List <users@tomcat.apache.org>
Date: Wed, 28 Jan 2009 09:09:40 -0600
Subject: RE: Servlet 2.5 and RequestDispatcher.include + Response.setHeader,
 	invalid?
Thread-Topic: Servlet 2.5 and RequestDispatcher.include +
 Response.setHeader, 	invalid?
Thread-Index: AcmBChqv60SVW+74RoW+jP1X5kfbzQAT8v7g
Message-ID: 
 <0AAE5AB84B013E45A7B61CB66943C17215B5C8998C@USEA-EXCH7.na.uis.unisys.com>
References: <497FEE3F.4090103@kensystem.com>
In-Reply-To: <497FEE3F.4090103@kensystem.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

> From: Ken Johanson [mailto:tomcat-user@kensystem.com]
> Subject: Servlet 2.5 and RequestDispatcher.include +
> Response.setHeader, invalid?
>
> It's my understanding that servlet 2.5 loosened the requirement that a
> included/callee Servlet (and JSP?) cannot set the resp headers/status,
> and should now be able to set them if not already committed.

Why do you think your "understanding" would override an explicit statement =
in the spec?  Here's the exact text from SRV.8.3 of the servlet spec versio=
n 2.5mr6:

"It cannot set headers or call any method that affects the headers of the r=
esponse, with the exception of the HttpServletRequest.getSession() and Http=
ServletRequest.getSession(boolean) methods. Any attempt to set the headers =
must be ignored, and any call to HttpServletRequest.getSession() or HttpSer=
vletRequest.getSession(boolean) that would require adding a Cookie response=
 header must throw an IllegalStateException if the response has been commit=
ted."

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MA=
TERIAL and is thus for use only by the intended recipient. If you received =
this in error, please contact the sender and delete the e-mail and its atta=
chments from all computers.

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