[
https://issues.apache.org/jira/browse/SLING-12478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remo Liechti updated SLING-12478:
---------------------------------
Description:
Add more information to the log about potential origins of the violation
message added in SLING-12454.
Use the RequestProgressTracker API to get the messages to find START_TIMER's
that do not have an END_TIMER yet, which means a violation is most likely
caused by that origin.
was:
In SLING-11722 a new configuration has been added to now allow any
{{content-type}} overrides from included scripts. This configuration either
allows the overrides or makes the rendering fail with an exception.
Another useful option, at least for applications in production relying on the
old behaviour, would be to allow to warn and not fail.
> Add potential origins of violations to the RequestDispatcher include API
> ------------------------------------------------------------------------
>
> Key: SLING-12478
> URL: https://issues.apache.org/jira/browse/SLING-12478
> Project: Sling
> Issue Type: Improvement
> Components: Engine
> Reporter: Remo Liechti
> Assignee: Radu Cotescu
> Priority: Minor
> Fix For: Engine 2.15.18
>
>
> Add more information to the log about potential origins of the violation
> message added in SLING-12454.
> Use the RequestProgressTracker API to get the messages to find START_TIMER's
> that do not have an END_TIMER yet, which means a violation is most likely
> caused by that origin.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
