Http request node always return httpresponsecodeerror

[Clubiy]

Self Checks

• 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.

Content

It was still available normally before, but after repeated testing several times, the http request node kept reporting errors. Any friends who have encountered similar problems? Wanna a solution, please!

[dosubot[bot]]

A persistent HTTPResponseCodeError (400) from the HTTP request node usually means the server is rejecting the request due to malformed or invalid parameters. Common causes include missing or invalid API keys, malformed JSON or form-data, incorrect Content-Type headers, or missing required fields in the payload.

A recent update now enforces API key validation: if the API key is empty or only whitespace, the node will fail early with a clear error. Before this, empty API keys could cause cryptic 400 errors or invalid headers, so double-check your API key configuration if you use bearer, basic, or custom auth types. Make sure the key is present and valid in the node settings, especially if you recently changed credentials or templates. See details

To troubleshoot:

• Inspect the node’s process_data or logs to see the actual request being sent (URL, headers, body).
• Check for malformed JSON, double-escaped strings, or missing required fields in your request body.
• For form-data, ensure Content-Type is not manually set if files are present—Dify handles this automatically.
• If you use variables or templates, verify they resolve to valid values at runtime.

If the error persists, try restarting Dify or clearing any cached state, and capture the full request/response for further diagnosis.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

   

[Clubiy]

@dosu
Maybe I found something, when I inserted the output of the other node into the json in the http request node as a string variable, I found in the conversation log that there was an extra "/" at the end of the inserted string, which prevented the request from proceeding.

[Clubiy]

@dosu
How could I remove the extra "/"?

[dosubot[bot]]

Dify doesn't currently provide built-in string manipulation functions (like trim or replace) directly in the workflow node UI or variable templates. To remove a trailing "/" from a variable, you have a couple of options:

• If you can preprocess the variable in an upstream node (for example, in a custom/script node or before passing it to the HTTP request node), use a JavaScript expression like yourString.replace(/\/$/, "") to strip the trailing slash.
• If you control the source node, ensure it outputs the value without the trailing "/" in the first place.

If neither is possible, you may need to handle this cleanup outside Dify before passing the value into the workflow.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}