You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Bertrand Delacretaz (JIRA)" <ji...@apache.org> on 2016/02/05 15:39:40 UTC

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

     [ https://issues.apache.org/jira/browse/SLING-5489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bertrand Delacretaz resolved SLING-5489.
----------------------------------------

Implemented in revision 1728673 based on the patch that I created for SLING-5274. I have added a comment that people shouldn't grab the SlingRequestProgressTracker from the request attributes, as suggested by Carsten.

> 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)