Router should return Content-Type header
#636
Assignees
Labels
Comments
garypen
added a commit
that referenced
this issue
Mar 15, 2022
If we haven't already set a Content-Type header, then make sure that we set one with a value of "application/json". fixes: #636
garypen
added a commit
that referenced
this issue
Mar 15, 2022
* Router should return Content-Type header If we haven't already set a Content-Type header, then make sure that we set one with a value of "application/json". fixes: #636
|
Is this still working? With v0.9.0+ the Content-Type header is not returned |
|
Seems not, I will re open it and fix it :) Thanks |
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
If the response is successful, I would expect the response from the router to have a response header of
Content-Type: application/json. Our subgraphs do, but the router doesn't so some tools complain because they look at this header to determine how to parse the response.Describe the solution you'd like
Router response includes header of
Content-Type: application/jsonDescribe alternatives you've considered
nil
Additional context
Current headers from Postman with response from router
The text was updated successfully, but these errors were encountered: