Hi
You actually also needs to add ?throwExceptionOnFailure=false to the
HTTP endpoint to be able return the various error codes as is.
In case eg the HTTP returns a http error 301 and you want it to be
returned as it to jetty.
PS: We should probably look into letting Jetty "understand"
HttpOperat
On Fri, Aug 7, 2009 at 1:25 PM, Willem Jiang wrote:
> That's because other components in Camel 2.0 will use the Exchange.HTTP_URI
> and Exchange.HTTP_PATH to do some work.
>
> Maybe we can add an option in http endpoint to ignore these two headers if
> you still want to use the HTTP bridge as Camel
hese two headers
> if you still want to use the HTTP bridge as Camel 1.x.
>
> Willem
>
--
View this message in context:
http://www.nabble.com/Bridging-between-HTTP-endpoints-tp24861191p24863993.html
Sent from the Camel - Users mailing list archive at Nabble.com.
That's because other components in Camel 2.0 will use the
Exchange.HTTP_URI and Exchange.HTTP_PATH to do some work.
Maybe we can add an option in http endpoint to ignore these two headers
if you still want to use the HTTP bridge as Camel 1.x.
Willem
_Jens wrote:
Hi,
in Camel 1.x you could w
sed to work now or is it worth to submit
a bug report for this? Are there any other properties that should be removed
to ensure that the to() really sends it to the destination it is supposed
to?
Thanks,
Jens
--
View this message in context:
http://www.nabble.com/Bridging-between-HTTP-endpoints-tp24861191p24861191.html
Sent from the Camel - Users mailing list archive at Nabble.com.
