You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Tobias Bocanegra (JIRA)" <ji...@apache.org> on 2011/04/06 22:04:05 UTC
[jira] [Resolved] (SLING-2049) Wrong URL unescaping
[ https://issues.apache.org/jira/browse/SLING-2049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tobias Bocanegra resolved SLING-2049.
-------------------------------------
Resolution: Invalid
sorry my bad. the %20 actually works. i.e. if there is a resource at "/content/foo test" it is resolved. the error lies in the servlet container that did not produce the correct url.
> Wrong URL unescaping
> --------------------
>
> Key: SLING-2049
> URL: https://issues.apache.org/jira/browse/SLING-2049
> Project: Sling
> Issue Type: Bug
> Reporter: Tobias Bocanegra
> Priority: Minor
>
> there is a difference when requesting with or without an escaped url. for example:
> curl -v -u admin:admin "http://localhost:4502/content/foo test.html"
> ...
> <p>The requested URL /content/foo was not found on this server.</p>
> and
> curl -v -u admin:admin "http://localhost:4502/content/foo%20test.html"
> ...
> <p>The requested URL /content/foo%20test.html was not found on this server.</p>
> Expected that the %20 is unescaped before resolved.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira