[ https://issues.apache.org/jira/browse/CXF-6015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14144686#comment-14144686 ]
Daniel commented on CXF-6015: ----------------------------- Probably the {{java.net.URI}} class is not a very good example as the RFC2396 that is referenced in the Javadocs of the {{java.net.URI}} constructors is obsoleted by the already mentioned RFC3986 that describes valid URIs for JAX-RS 2.0 (JSR339). > 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üdiger/Rü%3Bdiger}} > will result in {{anAttribute=Rü, anotherAttribute=Rüdiger}} to > be returned. -- This message was sent by Atlassian JIRA (v6.3.4#6332)