[
https://issues.apache.org/jira/browse/SLING-2353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13186755#comment-13186755
]
Felix Meschberger commented on SLING-2353:
------------------------------------------
> I personally would consider this a programming error but then I wouldn't have
> allowed null in the first place
That's not correct ;-) It has always been considered a valid use case to
redirect to self by *not* specifying either the resource or the path attribute.
This is fine, I hold this has been designed like this and works perfectly.
What I really consider a programming error is explicitly state resource=null as
in the original issue comment. So, not specifying resource at all and
explicitly setting it to null is not the same: The former is supported by
design the latter really is a programming error IMHO.
> 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
