camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadrian Zbarcea (Updated) (JIRA)" <>
Subject [jira] [Updated] (CAMEL-4954) Camel 2.9.0 incapable of working with % in endpoint URIs
Date Thu, 02 Feb 2012 14:51:53 GMT


Hadrian Zbarcea updated CAMEL-4954:

    Fix Version/s: 2.10.0
> Camel 2.9.0 incapable of working with % in endpoint URIs
> --------------------------------------------------------
>                 Key: CAMEL-4954
>                 URL:
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 2.9.0
>         Environment: Mac 10.7 Java 1.6.0_29
>            Reporter: Sebastian Rühl
>            Assignee: Hadrian Zbarcea
>            Priority: Critical
>             Fix For: 2.9.1, 2.10.0
>         Attachments:
> In the class org.apache.camel.util.URISupport which will be used to resolve endpoints
(DefaultCamelContext#normalizeEndpointUri) the method parseParameters will be called.
> At first the will be called with according to the javadoc "Returns
the decoded query component of this URI" returns a decoded URI. If that fails the
method will be called which according to the javadoc "Returns the decoded scheme-specific
part of this URI." returns a decoded URI.
> So to summarize we get in any case a decoded URI.
> This URI will then be than in the method org.apache.camel.util.URISupport#parseQuery(String)
again decoded with,String).
> This code leads to the following behaviour:
>  If a % is properly encoded with %25test the %25test will be substituted by the first
call to %test and the decoded again which leads to an Exception.
> In the commit you can
see that the % was uncommented from org.apache.camel.util#UnsafeUriCharactersEncoder. Maybe
this is related.
> However... Double encoding of URIs seems quite odd. With any URI char there is no issue
with that. But with % the % will be decoded again, which makes a % unusable in Camel.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message