You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2018/04/21 08:31:00 UTC
[jira] [Updated] (CAMEL-12462) toD with HTTP endpoints - Optimise
dynamic query to leverage HTTP_QUERY header
[ https://issues.apache.org/jira/browse/CAMEL-12462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen updated CAMEL-12462:
--------------------------------
Fix Version/s: 2.22.0
> toD with HTTP endpoints - Optimise dynamic query to leverage HTTP_QUERY header
> ------------------------------------------------------------------------------
>
> Key: CAMEL-12462
> URL: https://issues.apache.org/jira/browse/CAMEL-12462
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Major
> Fix For: 2.22.0
>
>
> We can consider for some HTTP components that support dynamic parts of their endpoints from Camel headers such as HTTP_QUERY and others.
> We can then in toD detect those components and then build a processor chain that does
> # setHeader - set dynamic header HTTP_QUERY
> # toD - call the endpoint with a more static uri
> This optimises to reuse the toD with more static uris, especially if you hit the same host for each toD and its only the query parameters that are dynamic.
> Today developers would need to use setHeader and to combo to do this, instead of a single toD.
> The trick is to separate the query parameters and the endpoint parameters and only set query parameters in the setHeader, and the endpoint parameters in toD.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)