fix(GraphQL): Pass on HTTP request headers for subscriptions #7806
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR passes the HTTP headers for a subscription request using the
RequestHeader
context key to theSubscribe
call.Earlier, the
Header
key in the context supported passing the headers to theSubscribe
call, but that required one to send an init request for the subscription with the init payload being set to a JSON object representing theHeader
.It is not possible in Dgraph cloud to modify the request payload, so we need to make this change.
Later, we should find one permanent fix for passing the HTTP headers for subscriptions. Also, our port of the
graphql-transport-ws
lib is far behind the source, so we should update that at some point.This change is