cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Will Gomes (JIRA)" <>
Subject [jira] Commented: (CXF-1820) CXF does not work with hex-encoded request parameters
Date Wed, 24 Sep 2008 14:04:44 GMT


Will Gomes commented on CXF-1820:

Could this be related to UrlUtilities.getStem() method? I posted a question [1] where wsdl
query request was not recoginezed because getStem() was parsing an decoded url (even if an
encoded url was passed in).

> CXF does not work with hex-encoded request parameters
> -----------------------------------------------------
>                 Key: CXF-1820
>                 URL:
>             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.

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

View raw message