You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wink.apache.org by "Luciano Resende (JIRA)" <ji...@apache.org> on 2013/03/17 17:55:14 UTC
[jira] [Commented] (WINK-361) Wink cannot resolved URI path
segments that have encoded forward slashes
[ https://issues.apache.org/jira/browse/WINK-361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13604653#comment-13604653 ]
Luciano Resende commented on WINK-361:
--------------------------------------
Could you please provide a simple resource and the code you are using to reproduce this issue (e.g. curl versus wink client code).
> Wink cannot resolved URI path segments that have encoded forward slashes
> -------------------------------------------------------------------------
>
> Key: WINK-361
> URL: https://issues.apache.org/jira/browse/WINK-361
> Project: Wink
> Issue Type: Bug
> Components: Server
> Affects Versions: 1.1.3
> Environment: Any
> Reporter: BK Lau
> Priority: Blocker
> Labels: Encoding, URI, forward, slashes
>
> Wink cannot resolve URI that have encoded forward slashes in them.
> Example: Consider the URI:
> /servers/{server}
> If the URI template parameter {server} is "http://abc.com:8000",
> one would get "404- Not Found" because of the "//" slashes
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira