GraphQL responses are treated as file

[DavideDelbiancoZucchetti]

Self Checks

• This is only for bug report, if you would like to ask a question, please head to Discussions.
• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
• [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
• Please do not modify this template :) and fill in all the required fields.

Dify version

0.11.2

Cloud or Self Hosted

Cloud, Self Hosted (Docker), Self Hosted (Source)

Steps to reproduce

Create an HTTP node that executes a POST request to a graphQL endpoint

✔️ Expected Behavior

The response should be in the body property and not in file

❌ Actual Behavior

Because of a change in PR #8818 a variable name NON_FILE_CONTENT_TYPES was introduced in api/core/workflow/nodes/http_request/entities.py and breaks graphql responses that have content type: "application/graphql-response+json; charset=utf-8"

[dosubot]

Hello @DavideDelbiancoZucchetti! I'm here to assist you with any bugs, questions, or contributions. Let's dive into the issue and work together to find a solution.

The issue you're experiencing is due to the introduction of the NON_FILE_CONTENT_TYPES variable in entities.py, which does not include the content type "application/graphql-response+json; charset=utf-8". This causes GraphQL responses to be incorrectly treated as files. To resolve this, you should add "application/graphql-response+json" to the NON_FILE_CONTENT_TYPES tuple in the code. Here's how you can modify it:

NON_FILE_CONTENT_TYPES = (
    "application/json",
    "application/xml",
    "text/html",
    "text/plain",
    "application/x-www-form-urlencoded",
    "application/graphql-response+json",
)

This change will ensure that GraphQL responses with the specified content type are handled correctly ^[1].

To continue talking to Dosu, mention @dosu.

[laipz8200]

Link to #10862