[jira] Closed: (SLING-994) DefaultGetServlet shoud not use sendError when response is already committed

["Carsten Ziegeler (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SLING-994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler closed SLING-994.
----------------------------------

    Resolution: Fixed

If the request is included, do not use sendError but throw an exception if no renderer is found - changed in Revision 783017

> DefaultGetServlet shoud not use sendError when response is already committed
> ----------------------------------------------------------------------------
>
>                 Key: SLING-994
>                 URL: https://issues.apache.org/jira/browse/SLING-994
>             Project: Sling
>          Issue Type: Bug
>          Components: Servlets Get
>    Affects Versions: Servlets Get 2.0.4
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>             Fix For: Servlets Get 2.0.6
>
>
> If no renderer servlet is found in the DefaultGetServlet, it calls sendError(). If this is an included request, sendError usually fails as the response is already committed. In this case it's hard to detect the underlying problem.
> Therefore I suggest to check if this is an included request and in this case throw a ServletException
> I'm not in favour of checking for response isCommitted as this is more unpredictable

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.