Thanks Zoran for getting back to me.
I will take a look at HttpBinding, but certainly this is very confusing.
From what I have seen, both the Query and Path parameters are being put in
message headers (good), but then the filter is removing the query parameters
(bad) and not the path
query Hi Alex,
perhaps I can shed some light on this, the header in header filter
strategy refers to Camel message headers and external (say HTTP)
headers. I think (haven't looked at the code) that the query
parameters are put in the message headers and it seems that the path
parameters are not. I
The other inconsistence is that path parameters defined in the Rest DSL are
copied to Exchange headers without any issue, i.e., unaffected by the header
filter strategy. So we end up with:
Path parameters unaffected by header filter.
Query parameters affected by header filter.
I would think
Look like it is caused by my:
Which is very strange, since the ones that have default value are not being
filtered.
However my intention (when using the header filter strategy) is to filter
incoming HTTP request headers, not to the headers that are copied from the
query
Hello:
Running Camel 3.0.1. I have a Rest DSL, where Query Params are not being
copied to the Exchange
