[SLING-1086] SlingRequestDispatcher must not include redirect resources as is

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: Engine 2.0.4
• Component/s: Engine
• Assignee: Felix Meschberger
• Reporter: Felix Meschberger
• Created: 14/Aug/09 18:57
• Updated: 26/Aug/10 21:00
• Resolved: 26/Aug/10 20:53

Description

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)

Issue Links

• duplicates: SLING-1087 RedirectServlet must not redirect if the response is committed or in included requests