[
https://issues.apache.org/jira/browse/HTTPCLIENT-1831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16298988#comment-16298988
]
Michael Hewitt commented on HTTPCLIENT-1831:
--------------------------------------------
*An update.*
After noticing that Camel is added the '//' internally to the URI I was
suspicious if maybe I could also use a '//' in the string URI I set as an
endpoint. Even though the Camel URI description does not document it this way.
So I set the topic as the host in the URIBuilder and set the string
"kafka://TestTopic?brokers=localhost%3A9092&valueDeserializer=org.apache.kafka.common.serialization.ByteArrayDeserializer"
as the endpoint URI.
This worked and Camel interpreted it properly. I guess I should have been
suspicous with Camel also managing the properly escaped ':' character as being
able to interpret a properly formated URI instead of the string they define the
URI as in the documentation.
So please disregard my comments above. This '/' change is no longer an issue
with Camel URIs. I just wish Camel documented their URIs better and I would not
have tried to set the topic as the path and instead used the host.
Sorry for the trouble. And thanks again for the fast response.
Cheers
> Possible bug in URIBuilder
> --------------------------
>
> Key: HTTPCLIENT-1831
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1831
> Project: HttpComponents HttpClient
> Issue Type: Bug
> Components: HttpClient (classic)
> Affects Versions: 4.5.3
> Reporter: Ivan Budincevic
> Labels: bug
> Fix For: 4.5.4, 4.6 Alpha1, 5.0 Alpha3
>
>
> While using the URIBuilder class to add a query parameter to a url using the
> addParameter(String param, String value) method, the output of this method
> would always append a "/" to the beginning of the url.
> The problem was first noticed for urls that contained "./" at the beginning,
> with the resulting url output from addParameter having "/./" at the
> beginning, The attempted fix was to remove the "./" part of the urls in order
> to have a relative http path, but using this method would still append a "/"
> to the beginning, converting the url path to an absolute path instead of the
> original relative path.
> This problem did not occur with versions previous to 4.5.3
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
