Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

subgraph response parts aren't propagated #1094

Closed
garypen opened this issue May 18, 2022 · 0 comments · Fixed by #1095
Closed

subgraph response parts aren't propagated #1094

garypen opened this issue May 18, 2022 · 0 comments · Fixed by #1095
Assignees

Comments

@garypen
Copy link
Contributor

garypen commented May 18, 2022

When the router calls a subgraph service, we take the response process the body and do some general validation to ensure the GraphQL looks right before returning the response back through the pipeline. The rest of the response is discarded. This means any headers returned from a subgraph don't make their way back into the response.

This is not a good outcome and it results in issues in the pipeline where plugin authors (in rhai or rust) expect to be able to interact with subgraph headers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants