[jira] [Comment Edited] (CAMEL-19188) GraphQL component should support Exchange.HTTP_QUERY or custom headers

["Claus Ibsen (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CAMEL-19188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17703887#comment-17703887 ] 

Claus Ibsen edited comment on CAMEL-19188 at 3/23/23 5:33 AM:
--------------------------------------------------------------

The component can become lenient properties like http components, so you can append any kind of parameters you like in the uri. And yeah also support for custom headers via a header is a good idea. 

Using HTTP_QUERY may not be idea if you do

from x
  to http
  to graphql

or 

from servlet/platform-http
   to graphql

As then HTTP_QUERY headers from the http component may interfere. We may use a new header in graphql only for this instead.


was (Author: davsclaus):
The component can become lenient properties like http components, so you can append any kind of parameters you like

> 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)