Luca Burgazzoli created CAMEL-11795:
---------------------------------------
Summary: service-call : service-call expression should have a way
to manipulate headers
Key: CAMEL-11795
URL: https://issues.apache.org/jira/browse/CAMEL-11795
Project: Camel
Issue Type: Improvement
Components: camel-core
Reporter: Luca Burgazzoli
Assignee: Luca Burgazzoli
Priority: Minor
Fix For: 2.21.0
>From apache-camel:
{code}
<lburgazzoli> davsclaus, I'm looking at CAMEL-11711
(Camel-example-spring-cloud-servicecall doesn't work out of the box)
<lburgazzoli> the issue is that
<lburgazzoli> there are some headers like CamelHttpPath now
<lburgazzoli> so i.e. undertow builds the effective url to incoke combining the
http uri you give it with info from the headers
<lburgazzoli> so the final call is not more like http://localhost:9012 but it
is http://localhost:9012/camel/serviceCall/service1
<lburgazzoli> which does not exists
<lburgazzoli> see this gist
https://gist.github.com/lburgazzoli/1a44497db3cb29d2370ee2d125bb741c
<davsclaus> ah yeah you need to remove the CamelHttp* headers
<davsclaus> i guess maybe camel-undertow has been "fixed" since that example
was created
<davsclaus> if you use something else like jetty it may have had that "problem"
from the beginning
<davsclaus> i guess maybe service call eip should disregard those headers or
something? unless you use those expression stuff etc
<davsclaus> where the expression evaluated the url of the service etc
{camel}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
