[jira] Closed: (SLING-434) DefaultGetServlet should check for a NonExistingResource before dispatching to renderers

["Felix Meschberger (JIRA)" <ji...@apache.org>]

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

Felix Meschberger closed SLING-434.
-----------------------------------

    Resolution: Fixed

Fixed in Rev. 654210 by moving the NonExistingResource check from the StreamRendererServlet to the DefaultGetServlet.

> DefaultGetServlet should check for a NonExistingResource before dispatching to renderers
> ----------------------------------------------------------------------------------------
>
>                 Key: SLING-434
>                 URL: https://issues.apache.org/jira/browse/SLING-434
>             Project: Sling
>          Issue Type: Improvement
>          Components: Default Servlets
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>             Fix For: 2.0.0
>
>
> The DefaultGetServlet dispatches the requests to the actual renderes based on the request extension. It does not currently check whether the resource underlying the request actually exists. Rather - by coincidence - this check is executed by the StreamRendererServlet. "By Coincidence" because a request for a non existing resource has no request extension which causes the StreamRendererServlet being selected for rendering.
> Better is for the DefaultGetServlet to check for the NonExistingResource and fail "early" before dispatching.

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