Thanks Siano, you are right. The header has the following properties;
[code]
CamelHttpResponseCode = 302
location = http://www.google.com.mt/?gws_rd=cr=
[/code]
I now understand; the correct body is being sent back to the browser but
without removing the headers the browser sees the 302 status
: Donnerstag, 22. September 2016 13:35
To: users@camel.apache.org
Subject: Re: Why is the set body not being returned?
Hello again. It seems that it is something in the headers. I have added
".removeHeaders("*")" to the chain and now jetty is correctly returning the
set message th
Hello again. It seems that it is something in the headers. I have added
".removeHeaders("*")" to the chain and now jetty is correctly returning the
set message through the "transform" call.
i.e. this works -
[code]
from("jetty:http://localhost:8080;)
.transform(constant(""))
I would think it is because the setbody is setting the body in the IN
exchange and the response you get is from the OUT exchange due to the
request/reply nature of your operation. It works similarly with RabbitMQ
where you have to set exchangePattern to InOut to get request/reply. If you
log the
