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

Posted to dev@sling.apache.org by "Joel Richard (JIRA)" <ji...@apache.org> on 2015/06/12 16:27:00 UTC

[jira] [Commented] (SLING-4584) Performance: XSSAPI.getValidHref should not be based on HTML filtering

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

Joel Richard commented on SLING-4584:
-------------------------------------

[~radu.cotescu], Antonio has just told me that this is your area and that it would be better if you could have a look at it. Do you have some time for it? By the way, the patch is just so big because I had to copy a config file for the tests.

> Performance: XSSAPI.getValidHref should not be based on HTML filtering
> ----------------------------------------------------------------------
>
>                 Key: SLING-4584
>                 URL: https://issues.apache.org/jira/browse/SLING-4584
>             Project: Sling
>          Issue Type: Improvement
>          Components: Extensions
>    Affects Versions: XSS Protection API 1.0.2
>            Reporter: Joel Richard
>              Labels: perfomance, xss
>             Fix For: XSS Protection API 1.0.4
>
>         Attachments: 0001-SLING-4584-Performance-XSSAPI.getValidHref-should-no.patch
>
>
> Around 3% of the rendering time is spent in getValidHref because it uses AntiSamy (which is a HTML filter) to do the job. This is obviously a hack and adds a lot of unnecessary overhead.



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