Metadata HTTP forwarding about rejoiner HOT 3 OPEN

Rejoiner doesn't. It cannot know what metadata is important to you and how it should be transmitted.

But in your endpoint, which can be a standard servlet, you can collect any metadata you like into an object of your choice and stick it into the ExecutionInput as "context". This context is available in any @Query or @SchemaModification annotated method from the DataFetchingEnvironment parameter.

from rejoiner.

@FrancoisChastel Did that answer you question? How would you like it to work? Is there something we can automate?

from rejoiner.

@siderakis I think having in the query in the gRPC-side something like a context object in the proto-definition of the services which contains the usual HTTP metadata as mentioned would be a great improvement, we could have a seamless experience of the rejoiner integration with the HTTP-Rest "world"

from rejoiner.