-
Notifications
You must be signed in to change notification settings - Fork 837
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
Invalid GraphQL Response #12322
Comments
@tim-hanssen Can you share the Postman app version where you notice this behaviour? |
Sure! I'm using |
Can you share the steps to reproduce this issue? Any public endpoint to test this? |
I think this happens when the content type is not matching |
Still exists in |
Hi @tim-hanssen I've found the source of the issue and I'm fixing it now. I'll update this issue once it's been released. |
This was fixed in v10.20, thanks again for reporting the issue. |
Is there an existing request for this feature?
Is your feature request related to a problem?
Since the new update it's not possible to display the raw body sent by a server if the request is done in GraphQL mode. The response shows an postman error "Received an invalid GraphQL response". This is very annoying when debugging GraphQL server errors.
Describe the solution you'd like
Setting to make it possible to view the raw body.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: