Multipart form-data boundary override in cloud version

Questions
,
1

Describe the problem/error/question

In the n8n cloud it seems that custom multipart form-data boundaries are overidden somehow. I think it happened after the update to 1.89.2. When running the same version locally via npx, the code executes fine and the boundary returned by httpbin is the same.

In the workflow, the last code node creates a http request and sets the Content-Type header to multipart/form-data; boundary=---011000010111000001101001. Strangely, the response by httpbin indicates that the header was altered to multipart/form-data; boundary=--------------------------936607543361292472435256. This causes failing requests at some other API we use.

Does anybody know why the header is overriden?

What is the error message (if any)?

Please share your workflow

Share the output returned by the last node

[
  {
    "headers": {
      "Accept": "application/json, text/plain, */*",
      "Accept-Encoding": "gzip, compress, deflate, br",
      "Content-Length": "28729",
      "Content-Type": "multipart/form-data; boundary=--------------------------936607543361292472435256",
      "Host": "httpbin.org",
      "User-Agent": "n8n",
      "X-Amzn-Trace-Id": "Root=1-68172509-7ef4369f598cae465b95159f"
    }
  }
]

Information on your n8n setup

  • n8n version: 1.89.2
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app): cloud
  • Operating system: