[ https://issues.apache.org/jira/browse/SLING-10391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17754178#comment-17754178 ]
Stefan Seifert commented on SLING-10391: ---------------------------------------- hmm, i think that ticket does not help much. the SLF4J based ESAPI LogFactory implementation is already configured in the Sling XSS module - but the log messages above are written to stdout before ESAPI sets up it's own logging (intentionally). > Improve MockXSSAPIImpl > ---------------------- > > Key: SLING-10391 > URL: https://issues.apache.org/jira/browse/SLING-10391 > Project: Sling > Issue Type: Improvement > Components: Testing > Affects Versions: Testing Sling Mock 3.0.2 > Reporter: Henry Kuijpers > Assignee: Stefan Seifert > Priority: Major > Fix For: Testing Sling Mock 3.4.12 > > > 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.20.10#820010)