[
https://issues.apache.org/jira/browse/CAMEL-19188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17704196#comment-17704196
]
Claus Ibsen commented on CAMEL-19188:
-------------------------------------
1)
Yes that is what you need for lenient. And then you also need to extract the
"left over properties" when creating the endpoint which then becomes the query
parameters.
Its not super easy, maybe look at some of the other lenient components and see
what they do
2)
Yeah add support for that HTTP_QUERY as well
3)
Add unit tests
> 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: Improvement
> Components: camel-graphql
> Reporter: Felix Hoßfeld
> Priority: Major
>
> 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)
