[jira] Commented: (CXF-1820) CXF does not work with hex-encoded request parameters

["Sergey Beryozkin (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CXF-1820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12641371#action_12641371 ] 

Sergey Beryozkin commented on CXF-1820:
---------------------------------------

Fixed on 2.2-snapshot, will be fixed on 2.1.4-SNAPSHOT shortly

> CXF does not work with hex-encoded request parameters
> -----------------------------------------------------
>
>                 Key: CXF-1820
>                 URL: https://issues.apache.org/jira/browse/CXF-1820
>             Project: CXF
>          Issue Type: Bug
>          Components: REST
>    Affects Versions: 2.1.2
>         Environment: CXFG using Spring 2.5 and Jetty
>            Reporter: Tarjei Huse
>
> Hi, I got a service where I want to expose a resource that is defined by
> an url to a rssfeed, something like:
>     @GET
>     @Path("/{URL}/")
>     public Subscriber getSubscriber(@PathParam("URL") String url) {
>        ... do something with the url.
>     }
> Now, this does not work with normal urls, nor with urlencoded urls. Why
> urlencoded values do not work I do not know, but for normal values, it
> seems obvious (they contain '/'s). I've also tried base64 encoding the
> urls, but that didn't work either because sometimes the base64 encoded
> string contains slashes as well.
> After some discussions on the list[1], it was that this is a bug. I have also tested Jersey and standard hex-encoding works with jersey.
> Links:
> 1. http://mail-archives.apache.org/mod_mbox/cxf-users/200809.mbox/%3C48D8F7B9.9090408@scanmine.com%3E

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.