[ https://issues.apache.org/jira/browse/SLING-2353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13186782#comment-13186782 ]
Felix Meschberger commented on SLING-2353: ------------------------------------------ > However, the question is if we keep the current check or rely on recursion > detection. currently a <sling:include/> would not be allowed I'd remove the check and rely on recursion detection (see also Tobias' comment above) > 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 > Assignee: Carsten Ziegeler > Priority: Minor > Fix For: Scripting JSP-Taglib 2.1.4 > > > 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