[
https://issues.apache.org/activemq/browse/CAMEL-1111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-1111:
----------------------------------
Assignee: Claus Ibsen
> HttpProducer - Side effect of using URI-based endpoint config disables POST
> method use
> --------------------------------------------------------------------------------------
>
> Key: CAMEL-1111
> URL: https://issues.apache.org/activemq/browse/CAMEL-1111
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-http
> Affects Versions: 1.5.0
> Environment: Any
> Reporter: Jason Royals
> Assignee: Claus Ibsen
> Priority: Minor
> Fix For: 1.5.1, 2.0.0
>
>
> 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 (http://activemq.apache.org/camel/http.html), I made
> the same change to my endpoint to include {{?httpClient.SoTimeout=5000}}, and
> that's when the problems started.
> 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.
