You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Julian Sedding (Jira)" <ji...@apache.org> on 2021/02/15 10:18:00 UTC

[jira] [Commented] (SLING-9874) Allow adapting SlingHttpServletRequest and ResourceResolver to XSSAPI

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

Julian Sedding commented on SLING-9874:
---------------------------------------

Thanks [~radu] for reverting. This was still on my todo list. Would it help if I take care of the release?

> Allow adapting SlingHttpServletRequest and ResourceResolver to XSSAPI
> ---------------------------------------------------------------------
>
>                 Key: SLING-9874
>                 URL: https://issues.apache.org/jira/browse/SLING-9874
>             Project: Sling
>          Issue Type: New Feature
>          Components: XSS Protection API
>    Affects Versions: XSS Protection API 2.2.6
>            Reporter: Julian Sedding
>            Assignee: Julian Sedding
>            Priority: Minor
>             Fix For: XSS Protection API 2.2.8
>
>
> Most commonly an {{XSSAPI}} instance is needed when rendering a response body. In such circumstances, it can be cumbersome to retrieve the {{XSSAPI}} service. To add some convenience, it would be nice to be able to adapt a {{SlingHttpServletRequest}} or a {{ResourceResolver}} to an {{XSSAPI}} instance.
> *15.02.2021: This has been reverted in [commit dd7ff4b|https://github.com/apache/sling-org-apache-sling-xss/commit/dd7ff4b]*



--
This message was sent by Atlassian Jira
(v8.3.4#803005)