Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Date: Fri, 19 Sep 2014 14:37:33 +0000 (UTC)
From: "Sergey Beryozkin (JIRA)" <jira@apache.org>
To: issues@cxf.apache.org
Message-ID: <JIRA.12742689.1411121102000.76918.1411137453858@Atlassian.JIRA>
In-Reply-To: <JIRA.12742689.1411121102000@Atlassian.JIRA>
References: <JIRA.12742689.1411121102000@Atlassian.JIRA>
 <JIRA.12742689.1411121102513@arcas>
Subject: [jira] [Commented] (CXF-6015) Path parameters containing semicolon
 are truncated due to missing encoding
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Sergey Beryozkin commented on CXF-6015:
---------------------------------------

The String converter can be registered by default if a new property is set, to minimize the effort for the developer, please confirm using the converter works, and I'll deal with the optimization

> Path parameters containing semicolon are truncated due to missing encoding
> --------------------------------------------------------------------------
>
>                 Key: CXF-6015
>                 URL: https://issues.apache.org/jira/browse/CXF-6015
>             Project: CXF
>          Issue Type: Bug
>          Components: JAX-RS
>    Affects Versions: 2.7.12, 3.0.1
>         Environment: Apache Tomcat / 7.0.54
> Eclipse Jetty / 9.2.2
>            Reporter: Daniel
>         Attachments: cxf-test.zip
>
>
> If a REST service uses path parameters, these parameters must not contain any semicolon as the parameter value gets truncated after the semicolon by many runtime environments. For that reason especially the semicolon should be encoded while building the client proxy.
> I pinned this issue down to the usage of {{org.apache.cxf.jaxrs.utils.HttpUtils.pathEncode(String)}} during the creation of the request URI. Path parameters are encoded using a fixed list of characters ({{=@/:!$&\'(),;~}}) that are preserved in {{pathEncode(String)}}. While this is fine/needed for encoding a complete path it leads to problems if used for encoding single elements of a path like path parameters.
> Attached you'll find a minimal example project containing a simple REST service that returns the provided path parameters. If deployed on localhost:8080, a call to {{http://localhost:8080/cxf-test-service-0.1/cxf-test/R&uuml;diger/R&uuml%3Bdiger}} will result in {{anAttribute=R&uuml, anotherAttribute=R&amp;uuml;diger}} to be returned.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)