[
https://issues.apache.org/jira/browse/SLING-9874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17226052#comment-17226052
]
Julian Sedding edited comment on SLING-9874 at 11/4/20, 1:50 PM:
-----------------------------------------------------------------
Fixed in [commit
1d7559e|https://github.com/apache/sling-org-apache-sling-xss/commit/1d7559ef58dc1093c25f0b8ef360ab677b9c0d92].
was (Author: jsedding):
Fixed in [commit
ab7618b|https://github.com/apache/sling-org-apache-sling-xss/commit/ab7618bcff4b086455ba073cfa91b94dd905ae54].
> 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
