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

Henry Kuijpers updated SLING-10391:
-----------------------------------
    Description: 
MockXSSAPIImpl only has a few very simplistic method implementations (i.e. for 
encodeForHTML it returns the input as-is).

I think we can make some improvements to it, by:
* Use StringEscapeUtils.escapeHtml4() to do HTML escaping (so that we can at 
least see a difference in the output)
* Use StringEscapeUtils.escapeXml() to do XML escaping

etc.

  was:
MockXSSAPIImpl only has a few very simplistic method implementations (i.e. for 
encodeForHTML it returns the input as-is).

I think we can make some improvements to it, by:
* Use StringEscapeUtils.escapeHtml4() to do HTML escaping (so that we can at 
least see a difference in the output)
* Use StringEscapeUtils.escapeXml() to do XML escaping
etc.


> Improve MockXSSAPIImpl
> ----------------------
>
>                 Key: SLING-10391
>                 URL: https://issues.apache.org/jira/browse/SLING-10391
>             Project: Sling
>          Issue Type: Bug
>          Components: Testing
>    Affects Versions: Testing Sling Mock 3.0.2
>            Reporter: Henry Kuijpers
>            Priority: Major
>
> MockXSSAPIImpl only has a few very simplistic method implementations (i.e. 
> for encodeForHTML it returns the input as-is).
> I think we can make some improvements to it, by:
> * Use StringEscapeUtils.escapeHtml4() to do HTML escaping (so that we can at 
> least see a difference in the output)
> * Use StringEscapeUtils.escapeXml() to do XML escaping
> etc.



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

Reply via email to