[ https://issues.apache.org/jira/browse/SLING-2353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13184100#comment-13184100 ]
Felix Meschberger commented on SLING-2353: ------------------------------------------ I think null is a valid use case and has always been supported. The idea is to include "this" resource with some different selector and/or extension. We could prevent endless loops, if we would throw in this case where the target resource is this resource and no selector/extension overwrite is taking place. > 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