You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Jean-Christophe Kautzmann (JIRA)" <ji...@apache.org> on 2015/04/01 18:27:52 UTC

[jira] [Comment Edited] (SLING-4560) XSSAPI#getValidHref is empty for valid Bengali or Hindi characters

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

Jean-Christophe Kautzmann edited comment on SLING-4560 at 4/1/15 4:27 PM:
--------------------------------------------------------------------------

yes, that's the correct encoding in unicode:
中文 -> \u4E2D\u6587
⺁〡〢☉⊕〒 ->  \u2E81\u3021\u3022\u2609\u2295\u3012


was (Author: jck):
yes, that's the correct encoding in unicode.

> XSSAPI#getValidHref is empty for valid Bengali or Hindi characters
> ------------------------------------------------------------------
>
>                 Key: SLING-4560
>                 URL: https://issues.apache.org/jira/browse/SLING-4560
>             Project: Sling
>          Issue Type: Bug
>          Components: Extensions
>            Reporter: Jean-Christophe Kautzmann
>             Fix For: XSS Protection API 1.0.4
>
>
> I added (locally) 2 test cases to org.apache.sling.xss.impl.XSSAPIImplTest#testGetValidHref:
> {code}
> {"/etc/commerce/collections/中文", "/etc/commerce/collections/中文"},
> {"/etc/commerce/collections/⺁〡〢☉⊕〒", "/etc/commerce/collections/⺁〡〢☉⊕〒"},
> {code}
> the first test passes (chinese characters), the 2nd fails (bengali/hindi characters) although it should pass as they are valid characters.



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