[
https://issues.apache.org/jira/browse/SLING-5274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134166#comment-15134166
]
Carsten Ziegeler commented on SLING-5274:
-----------------------------------------
HttpContext#handleSecurity is the first thing that is called, then filters,
then the servlet
Right now we're using propriatary stuff from the Apache Felix implementation
for the context support. Therefore we should switch to the OSGi Http Whiteboard
implementation. If we do so, some things look a little bit different. So I
would do that migration first, and then we can revisit this issue and do it
right - whatever right than means
> Include authentication in RequestProgressTracker
> ------------------------------------------------
>
> Key: SLING-5274
> URL: https://issues.apache.org/jira/browse/SLING-5274
> Project: Sling
> Issue Type: Improvement
> Components: Engine
> Reporter: Alexander Klimetschek
> Attachments: SLING-5274.patch
>
>
> The request progress tracker only starts with the sling filters, after the
> sling authentication ran through. Since authentication steps can be complex
> with multiple handlers (just like filters) and can have a major performance
> impact (custom auth handlers, slow resource resolver login) it would be very
> useful to include it with detailed information.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
