Bug in binary data output of HTTP node?

Hi all.
When referencing the binary data from the HTTP node, $binary and items[0].binary contain differing, incomplete data.

Example workflow:

{
  "nodes": [
    {
      "parameters": {},
      "name": "Start",
      "type": "n8n-nodes-base.start",
      "typeVersion": 1,
      "position": [
        250,
        300
      ]
    },
    {
      "parameters": {
        "url": "https://picsum.photos/300/300",
        "responseFormat": "file",
        "options": {}
      },
      "name": "HTTP Request",
      "type": "n8n-nodes-base.httpRequest",
      "typeVersion": 1,
      "position": [
        420,
        300
      ]
    },
    {
      "parameters": {
        "functionCode": "console.log($binary);\nconsole.log(items[0].binary);\n\nreturn items;"
      },
      "name": "Function1",
      "type": "n8n-nodes-base.function",
      "typeVersion": 1,
      "position": [
        630,
        350
      ]
    },
    {
      "parameters": {
        "filePath": "/data/photo.jpg"
      },
      "name": "Read Binary File",
      "type": "n8n-nodes-base.readBinaryFile",
      "typeVersion": 1,
      "position": [
        426,
        450.666668176651
      ]
    }
  ],
  "connections": {
    "Start": {
      "main": [
        [
          {
            "node": "HTTP Request",
            "type": "main",
            "index": 0
          }
        ]
      ]
    },
    "HTTP Request": {
      "main": [
        [
          {
            "node": "Function1",
            "type": "main",
            "index": 0
          }
        ]
      ]
    }
  }
}

Received output:
(When binary data is received from the HTTP node)
image

Expected output:
(When binary data is received from a Read Binary File node)
image
Note: The data property seems to be missing from $binary.data here as well

Is this a bug in the HTTP node (and/or binary property) or something’s wrong in the way i’m implementing/understanding?

Thanks

The property $binary got created to make it easy to access the metadata of binary-data in expressions. The actual binary base64-encoded-data got excluded on purpose (here).