[jira] [Commented] (SLING-8742) Allow overriding the extension when using the RequestDispatcher

["Bertrand Delacretaz (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SLING-8742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17014145#comment-17014145 ] 

Bertrand Delacretaz commented on SLING-8742:
--------------------------------------------

Are these {{o.a.s.api}} changes a consequence of the "fat API bundle" syndrome of that API bundle, which contains much more actual code than it should? As opposed to being actual API changes.

If yes it might be a good time to tackle that fat bundle problem, which is also causing problems in other places lately (SLING-8962).

> Allow overriding the extension when using the RequestDispatcher
> ---------------------------------------------------------------
>
>                 Key: SLING-8742
>                 URL: https://issues.apache.org/jira/browse/SLING-8742
>             Project: Sling
>          Issue Type: Improvement
>          Components: API
>            Reporter: Robert Munteanu
>            Priority: Major
>             Fix For: API 2.22.2
>
>
> It is sometimes useful to be able to include another resource and override the extension at the same time.
> My scenario is that I am routing all requests through an entry point {{/content/maven.html}} and then serving resources based on the suffix.
> If I a binary file is requested, it should be downloaded ( by forcing the extension to be null ), but instead the html extension is used, which means the HTML Renderer kicks in.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)