[jira] [Commented] (SLING-5625) Unable to impersonate user with surrogate pair character

[ https://issues.apache.org/jira/browse/SLING-5625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15525035#comment-15525035 ] Christanto commented on SLING-5625: --- Also you can simplify the whole implementation simply by encoding

[jira] [Commented] (SLING-5625) Unable to impersonate user with surrogate pair character

[ https://issues.apache.org/jira/browse/SLING-5625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15525033#comment-15525033 ] Christanto commented on SLING-5625: --- [~asanso] BTW Since you encode when you set, you should also decode

[jira] [Commented] (SLING-5824) Servlet Filter to do POST tunnelling to GET

[ https://issues.apache.org/jira/browse/SLING-5824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15366125#comment-15366125 ] Christanto commented on SLING-5824: --- But this is just another GET request. I don't understand. >

[jira] [Commented] (SLING-5824) Servlet Filter to do POST tunnelling to GET

[ https://issues.apache.org/jira/browse/SLING-5824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15366105#comment-15366105 ] Christanto commented on SLING-5824: --- This is about converting POST to GET, not the other way around. >

[jira] [Commented] (SLING-5824) Servlet Filter to do POST tunnelling to GET

[ https://issues.apache.org/jira/browse/SLING-5824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15366061#comment-15366061 ] Christanto commented on SLING-5824: --- Yes the script is trivial. The code at issue description is pretty

[jira] [Commented] (SLING-5824) Servlet Filter to do POST tunnelling to GET

[ https://issues.apache.org/jira/browse/SLING-5824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15365997#comment-15365997 ] Christanto commented on SLING-5824: --- bq. IIUC this happens in client code, so what prevents you from

[jira] [Commented] (SLING-5824) Servlet Filter to do POST tunnelling to GET

[ https://issues.apache.org/jira/browse/SLING-5824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15365968#comment-15365968 ] Christanto commented on SLING-5824: --- bq. But once you start using POST from client, as you mentioned in

[jira] [Commented] (SLING-5824) Servlet Filter to do POST tunnelling to GET

[ https://issues.apache.org/jira/browse/SLING-5824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15364652#comment-15364652 ] Christanto commented on SLING-5824: --- GET is still preferable for the use case, as it allows bookmarking.

[jira] [Updated] (SLING-5824) Servlet Filter to do POST tunnelling to GET

[ https://issues.apache.org/jira/browse/SLING-5824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christanto updated SLING-5824: -- Description: Sometimes there is a case where the request URL is very long. For example, during

[jira] [Created] (SLING-5824) Servlet Filter to do POST tunnelling to GET

Christanto created SLING-5824: - Summary: Servlet Filter to do POST tunnelling to GET Key: SLING-5824 URL: https://issues.apache.org/jira/browse/SLING-5824 Project: Sling Issue Type: Improvement

[jira] [Commented] (SLING-5625) Unable to impersonate user with surrogate pair character

[ https://issues.apache.org/jira/browse/SLING-5625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15208338#comment-15208338 ] Christanto commented on SLING-5625: --- Encoding/decoding using URLEncoder/URLDecoder should work just

[jira] [Created] (SLING-5625) Unable to impersonate user with surrogate pair character

Christanto created SLING-5625: - Summary: Unable to impersonate user with surrogate pair character Key: SLING-5625 URL: https://issues.apache.org/jira/browse/SLING-5625 Project: Sling Issue Type:

[jira] [Commented] (SLING-4860) Vanity Path cannot be used for MergedResource (or virtual resource)

[ https://issues.apache.org/jira/browse/SLING-4860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14628405#comment-14628405 ] Christanto commented on SLING-4860: --- Any other solution to satisfy the requirement?

[jira] [Created] (SLING-4860) Vanity Path cannot be used for MergedResource (or virtual resource)

Christanto created SLING-4860: - Summary: Vanity Path cannot be used for MergedResource (or virtual resource) Key: SLING-4860 URL: https://issues.apache.org/jira/browse/SLING-4860 Project: Sling

[jira] [Commented] (SLING-4860) Vanity Path cannot be used for MergedResource (or virtual resource)

[ https://issues.apache.org/jira/browse/SLING-4860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14616710#comment-14616710 ] Christanto commented on SLING-4860: --- cc: [~cziegeler] Vanity Path cannot be used for

[jira] [Created] (SLING-2129) Support case insensitively for jcr:language search in JcrResourceBundle

Support case insensitively for jcr:language search in JcrResourceBundle --- Key: SLING-2129 URL: https://issues.apache.org/jira/browse/SLING-2129 Project: Sling Issue Type:

[jira] [Created] (SLING-2111) JcrResourceBundle is not compatible with RFC 3066

JcrResourceBundle is not compatible with RFC 3066 - Key: SLING-2111 URL: https://issues.apache.org/jira/browse/SLING-2111 Project: Sling Issue Type: Bug Components: JCR Affects