[
https://issues.apache.org/jira/browse/CAMEL-19188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17705409#comment-17705409
]
Felix Hoßfeld commented on CAMEL-19188:
---------------------------------------
I have filed [PR 9655|https://github.com/apache/camel/pull/9655] to address
point 1.) and 2.)
Point 2.) I would add later if necessary. Or use-case can be solved by
inserting properties into the uri.
> GraphQL component should support Exchange.HTTP_QUERY or custom headers
> ----------------------------------------------------------------------
>
> Key: CAMEL-19188
> URL: https://issues.apache.org/jira/browse/CAMEL-19188
> Project: Camel
> Issue Type: New Feature
> Components: camel-graphql
> Reporter: Felix Hoßfeld
> Priority: Major
> Fix For: 3.21.0, 4.0-M3, 4.0
>
>
> We are trying to access Pimcore through the camel-graphql component. It
> requires that an API-Key ist either send as a Query-Parameter (by appending
> "?apikey=123456" to the uri) or as a Header (".setHeader('x-api-key',
> constant('123456'))").
> At the moment neither approaches work because the additional parameter
> triggers the following error:
> There are 1 parameters that couldn't be set on the endpoint. Check the uri
> if the parameters are spelt correctly and that they are properties of the
> endpoint. Unknown parameters=[\{apikey=123456} And the headers in the
> incoming message are simply ignored.
> I think two approaches are possible to fix this: Either the component should
> support the Exchange.HTTP_QUERY-Header and append this to the uri or there
> should be an option to copy headers to the http message - preferable with a
> list or regex to limit the headers sent.
> What approaches do you recommend/prefer? I would be willing to provide a path
> for either.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
