You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2009/12/21 18:18:18 UTC

[jira] Closed: (SLING-1229) Enhance handling missing renderer situation in included requests

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

Carsten Ziegeler closed SLING-1229.
-----------------------------------


> Enhance handling missing renderer situation in included requests
> ----------------------------------------------------------------
>
>                 Key: SLING-1229
>                 URL: https://issues.apache.org/jira/browse/SLING-1229
>             Project: Sling
>          Issue Type: Bug
>          Components: Servlets
>    Affects Versions: Servlets Get 2.0.6
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>             Fix For: Servlets Get 2.0.8
>
>
> Currently the DefaultGetServlet either sends a 403/FORBIDDEN error if a desired renderer is not known or throws a ServletException in this case if the request is included. 
> This is not a good solution. It would better to just log an error message if the response is committed or the request included and only send the 403 error if the request is neither included nor the response committed.

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