[jira] Resolved: (SLING-1086) SlingRequestDispatcher must not include redirect resources as is

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

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

Felix Meschberger resolved SLING-1086.
--------------------------------------

      Assignee: Felix Meschberger
    Resolution: Duplicate

Duplicate of SLING-1087

> SlingRequestDispatcher must not include redirect resources as is
> ----------------------------------------------------------------
>
>                 Key: SLING-1086
>                 URL: https://issues.apache.org/jira/browse/SLING-1086
>             Project: Sling
>          Issue Type: Bug
>          Components: Engine
>    Affects Versions: Engine 2.0.4
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>
> When including a resource the SlingRequestDispatcher calls the ResourceResolver.resolve() method if the dispatcher has been created with a path instead of a resource. This method can return a redirect resource (a synthetic resource with resource type sling:redirect).
> In the case of request dispatching rendering a redirect resource will probably not be the desired result.
> Thus the SlingRequestDispatcher.dispatch method should be modified around line 145 (in Rev. 788719) to probably first call ResourceResolver.getResource() and only try resolve() if getResource() returns null.
> (info: resolve is called for ease of use to handle selector and extension overwrites for the included resource)

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