Sorry for the spamming. My thoughts are starting to run circles in my mind. :)
Ad 3)
I believe you could ignore the comment regarding CamelHttpRawQuery not beeing
URL encoded since it seems to be handled in HttpHelter.createURI(...). (I saw
the CamelHttpQuery and CamelHttpRawQuery headers beeing
A complement to my last mail.
Ad 3)
After some more investigation I realized that the http-component consumer
doesn't set the CamelHttpRawQuery header (so maybe it isn't a miss in the
documentation after all).
However, the header is still handled by the code I referenced in my last mail
when
Ad 1)
With path parameter I mean {name} in your example (or {id} and {somePathParam}
in the examples from my first mail).
Ad 2)
Does this mean that if I use toD with the http-component, optimization will
always be used no mather how I define the component path (e.g.
toD(http("dummyHost:8181/dum
Ad 1)
Do you mean path parameters such as "/foo/{name}" or what exactly?
Ad 2)
Its detected for components that support toD optimizations (only a
handful does) but most of the http based does.
Ad 3)
The toD http optimization logic is here
https://github.com/apache/camel/blob/main/components/camel
The most important questions (from my previously mail) which I hope to find an
answer to is:
1. How come the CamelHttpPath header is empty when a Camel REST DSL endpoint
doesn't consists of any path parameters? Is it by design or a bug?
2. In the toD documentation it says that for the optimisat
Hi,
I’m migrating several (around 20-30) Camel REST DSL projects from Camel 2.17 to
3.4. The projects use a similar solution pattern to route incoming calls to
backend systems with a similar URL as the Camel REST endpoints. E.g. when
calling:
http://localhost:8080/services/rest/dummy/lorem/i
