[
https://issues.apache.org/jira/browse/WINK-361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13608546#comment-13608546
]
BK Lau commented on WINK-361:
-----------------------------
Luciano:
I think there are 2 separate issues that are at play here:
1. Originally, I got "404- Not Found" before the Tomcat security fixes comes
out- this happens at the Wink layer as reported earlier.
2. After the Tomcat security fixes, it appears that the Wink layer was not hit
at all(?) and we got "HTTP/1.1 400 Bad Request".
So in summary, it would be a good thing to validate this against another
servlet container besides Tomcat because Tomcat security fixes could "mask" the
Wink defect.
> 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
