camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <>
Subject [jira] Commented: (CAMEL-1111) HttpProducer - Side effect of using URI-based endpoint config disables POST method use
Date Mon, 24 Nov 2008 09:23:05 GMT


Claus Ibsen commented on CAMEL-1111:

I think this is fixed in 1.5.1 where I recently fixed some related issues.

Basically it should remove the httpClient.XXX options from the URI so it will revert to POST.

However you can force it to use POST see the wiki

> HttpProducer - Side effect of using URI-based endpoint config disables POST method use
> --------------------------------------------------------------------------------------
>                 Key: CAMEL-1111
>                 URL:
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: camel-http
>    Affects Versions: 1.5.0
>         Environment: Any
>            Reporter: Jason Royals
>            Priority: Minor
> Hello all,
> I'm using Camel HTTP component to send data across to HTTP web services.  Of course we
need to POST this data over, and it's all been peachy until I started on a storycard to implement
error handling and retry on timeouts.
> Following the docco here (, I made the same
change to my endpoint to include {{?httpClient.SoTimeout=5000}}, and that's when the problems
> After stepping through the code, I have now found that Camel thinks "httpClient.soTimeout"
is actually a query string parameter that I want to pass across to the remote service, when
it is not - it's just a configuration option for the HTTPClient.  Perhaps Camel needs a QueryStringFilter
(or something like it) so that it can distinguish configuration options as opposed to real
GET method parameters, or maybe for now ignore any parameters beginning with {{httpClient}}.
> Filing as a bug for now because at the very least, the documentation should be updated
to highlight the limitation of only allowing GET methods when URI-based configuration is employed.
 I haven't identified a workaround yet (using Spring DSL) but I'm sure it won't be too difficult.
> Thanks!
> Jason

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message