users@grizzly.java.net

Re: Grizzly servlet HttpServletRequest.sendError and headers

From: Paul Sandoz <Paul.Sandoz_at_Sun.COM>
Date: Mon, 19 Oct 2009 17:31:15 +0200

On Oct 19, 2009, at 5:25 PM, Jeanfrancois Arcand wrote:

> Salut,
>
> Paul Sandoz wrote:
>> On Oct 19, 2009, at 4:52 PM, Jeanfrancois Arcand wrote:
>>> Salut,
>>>
>>> Paul Sandoz wrote:
>>>> Hi,
>>>> I noticed there is a bug in the Grizzly servlet support in 1.9.19-
>>>> SNAPSHOT.
>>>> If i call sendError then any headers set after that call will not
>>>> be sent in the response.
>>>
>>> OK I will take a look.
>>>
>> Thanks.
>>>> This is a bug that manifested itself in GF v3 and was fixed at
>>>> some point (i think it is still in GF v2.1).
>>>
>>> In v3, are you running Jersey on top of the WebContainer or
>>> Grizzly Servlet Container?
>> The former i think i.e. just normal war deployment.
>
> Oh then you need to file a bug in v3 instead (sorry for that).
>

I think there be some confusion!

I meant the bug occurs in the Grizzly servlet container 1.9.19-
SNAPSHOT. I am fixing Jersey to work around the silly restriction for
JSP error pages that requires that sendError be called rather that
setStatus.

The same behavior also manifested itself in a version of GF v3
(perhaps prelude?) and was subsequently fixed (by Jan i think). So i
am guessing there may be some shared code...

Paul.