[
https://issues.apache.org/jira/browse/SLING-2353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13184927#comment-13184927
]
Carsten Ziegeler commented on SLING-2353:
-----------------------------------------
So, you agree that null is not a valid use case, right?
But in addition, we need to check for the inclusion of the same resource
without new extension or selector, otherwise an include of just resource="<%=
resource %> would end up in the same situation.
> Prevent <sling:include resource="<%= null %>" /> to include itself
> ------------------------------------------------------------------
>
> Key: SLING-2353
> URL: https://issues.apache.org/jira/browse/SLING-2353
> Project: Sling
> Issue Type: Bug
> Components: Scripting
> Affects Versions: Scripting JSP-Taglib 2.1.2
> Reporter: Tobias Bocanegra
> Priority: Minor
>
> If you add this sling:include to a JSP <sling:include resource="<%= null %>"
> />
> then it will cause the page to keep including itself recursively making the
> server slow. there is a recursion limitation though to prevent endless loops.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
