[jira] [Commented] (SLING-5489) Create the SlingRequestProgressTracker earlier (SlingHttpContext.handleSecurity)

["Bertrand Delacretaz (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SLING-5489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134270#comment-15134270 ] 

Bertrand Delacretaz commented on SLING-5489:
--------------------------------------------

With this change, even without SLING-5274 the tracker now includes minimal information about the authentication process, like this:

{code}
    168 COMMENT timer_end format is {<elapsed microseconds>,<timer name>} <optional message>
    229 LOG Method=GET, PathInfo=null
    257 TIMER_START{handleSecurity}
   2685 TIMER_END{2421,handleSecurity} authenticator org.apache.sling.auth.core.impl.SlingAuthenticator@4d6df3bf returns true
{code}

> Create the SlingRequestProgressTracker earlier (SlingHttpContext.handleSecurity)
> --------------------------------------------------------------------------------
>
>                 Key: SLING-5489
>                 URL: https://issues.apache.org/jira/browse/SLING-5489
>             Project: Sling
>          Issue Type: Improvement
>          Components: Engine
>    Affects Versions: Engine 2.4.6
>            Reporter: Bertrand Delacretaz
>            Assignee: Bertrand Delacretaz
>            Priority: Minor
>             Fix For: Engine 2.4.8
>
>
> For cases like SLING-5274 where we want to include authenticator information in the RequestTracker, that object should be made available earlier.
> Creating it in SlingHttpContext.handlerSecurity should be early enough for those purposes.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)