You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Konrad Windszus (Jira)" <ji...@apache.org> on 2023/02/03 18:42:00 UTC
[jira] [Commented] (SLING-11767) Disabled XML renderer is still used when configured in extension alias
[ https://issues.apache.org/jira/browse/SLING-11767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17683991#comment-17683991 ]
Konrad Windszus commented on SLING-11767:
-----------------------------------------
This was a deliberate decision introduced with SLING-6790 but I agree that this deserves a more explicit description in the alias.
> Disabled XML renderer is still used when configured in extension alias
> ----------------------------------------------------------------------
>
> Key: SLING-11767
> URL: https://issues.apache.org/jira/browse/SLING-11767
> Project: Sling
> Issue Type: Bug
> Components: Servlets
> Affects Versions: Servlets Get 2.1.44
> Reporter: Bjoern Weide
> Priority: Major
>
> When configuring an extension alias ("aliases") in the Sling Get servlet as
> {code:java}
> xml:pdf {code}
> that maps the pdf extension to the xml extension the content is rendered using the XML renderer, even when the XML renderer is disabled (via "enable.xml" = false).
> This can be reproduced via Sling 12 starter using
> {code:java}
> curl http://admin:admin@localhost:8080/content/starter.pdf{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)