You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Alexander Klimetschek (JIRA)" <ji...@apache.org> on 2009/09/24 22:58:16 UTC
[jira] Created: (SLING-1123) Atom Taglib: ids have wrong escaping
Atom Taglib: ids have wrong escaping
------------------------------------
Key: SLING-1123
URL: https://issues.apache.org/jira/browse/SLING-1123
Project: Sling
Issue Type: Bug
Components: Scripting
Reporter: Alexander Klimetschek
The atom taglib (contrib/scripting/jsp-taglib-atom) seems to do some wrong escaping for <id>s. When setting the id attribute of atom:entry with a normal path like /my/path, the output will be fully escaped in URL encoding: %2F%63%6F%6E%74%65%6E%74%2F%67%65%6F%6D
Looking at the code, in o.a.s.atom.taglib.EntryTagHandler.doEndTag(), it says:
if (id != null) entry.setId(UrlEncoding.encode(id));
which is probably wrong.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-1123) Atom Taglib: ids have wrong escaping
Posted by "Alexander Klimetschek (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-1123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexander Klimetschek resolved SLING-1123.
------------------------------------------
Resolution: Duplicate
> Atom Taglib: ids have wrong escaping
> ------------------------------------
>
> Key: SLING-1123
> URL: https://issues.apache.org/jira/browse/SLING-1123
> Project: Sling
> Issue Type: Bug
> Components: Scripting
> Reporter: Alexander Klimetschek
>
> The atom taglib (contrib/scripting/jsp-taglib-atom) seems to do some wrong escaping for <id>s. When setting the id attribute of atom:entry with a normal path like /my/path, the output will be fully escaped in URL encoding: %2F%63%6F%6E%74%65%6E%74%2F%67%65%6F%6D
> Looking at the code, in o.a.s.atom.taglib.EntryTagHandler.doEndTag(), it says:
> if (id != null) entry.setId(UrlEncoding.encode(id));
> which is probably wrong.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.